From: syzbot <syzbot+2a3b1b28cad90c608e20@syzkaller•appspotmail.com>
To: coreteam@netfilter•org, davem@davemloft•net, fw@strlen•de,
kadlec@netfilter•org, linux-kernel@vger•kernel.org,
netdev@vger•kernel.org, netfilter-devel@vger•kernel.org,
pablo@netfilter•org, syzkaller-bugs@googlegroups•com
Subject: Re: WARNING in nf_tables_table_destroy
Date: Thu, 23 Jan 2020 04:30:00 -0800 [thread overview]
Message-ID: <000000000000ba7772059ccdcc7b@google.com> (raw)
In-Reply-To: <00000000000014b040059c654481@google.com>
syzbot has bisected this bug to:
commit ec7470b834fe7b5d7eff11b6677f5d7fdf5e9a91
Author: Pablo Neira Ayuso <pablo@netfilter•org>
Date: Mon Jan 13 17:09:58 2020 +0000
netfilter: nf_tables: store transaction list locally while requesting module
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12c2ef59e00000
start commit: 5a9ef194 net: systemport: Fixed queue mapping in internal ..
git tree: net
final crash: https://syzkaller.appspot.com/x/report.txt?x=11c2ef59e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=16c2ef59e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e89bd00623fe71e
dashboard link: https://syzkaller.appspot.com/bug?extid=2a3b1b28cad90c608e20
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15338966e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1667d8d6e00000
Reported-by: syzbot+2a3b1b28cad90c608e20@syzkaller•appspotmail.com
Fixes: ec7470b834fe ("netfilter: nf_tables: store transaction list locally while requesting module")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-01-23 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 7:47 WARNING in nf_tables_table_destroy syzbot
2020-01-23 12:30 ` syzbot [this message]
2020-02-17 6:09 ` syzbot
2020-02-17 6:42 ` Florian Westphal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000ba7772059ccdcc7b@google.com \
--to=syzbot+2a3b1b28cad90c608e20@syzkaller$(echo .)appspotmail.com \
--cc=coreteam@netfilter$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=fw@strlen$(echo .)de \
--cc=kadlec@netfilter$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=pablo@netfilter$(echo .)org \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox