From: syzbot <syzbot+37a6804945a3a13b1572@syzkaller.appspotmail.com>
To: coreteam@netfilter.org, davem@davemloft.net, fw@strlen.de,
kadlec@blackhole.kfki.hu, kadlec@netfilter.org,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pablo@netfilter.org, syzkaller-bugs@googlegroups.com,
yoshfuji@linux-ipv6.org
Subject: Re: BUG: corrupted list in nf_tables_commit
Date: Thu, 16 Jan 2020 20:45:01 -0800 [thread overview]
Message-ID: <000000000000c31c6d059c4e9a6c@google.com> (raw)
In-Reply-To: <000000000000b3599c059c36db0d@google.com>
syzbot has bisected this bug to:
commit 7c23b629a8085b11daccd68c62b5116ff498f84a
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Sun Jan 7 00:04:22 2018 +0000
netfilter: flow table support for the mixed IPv4/IPv6 family
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=146472d1e00000
start commit: 51d69817 Merge tag 'platform-drivers-x86-v5.5-3' of git://..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=166472d1e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=126472d1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9290aeb7e6cf1c4
dashboard link: https://syzkaller.appspot.com/bug?extid=37a6804945a3a13b1572
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17241c76e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13118315e00000
Reported-by: syzbot+37a6804945a3a13b1572@syzkaller.appspotmail.com
Fixes: 7c23b629a808 ("netfilter: flow table support for the mixed IPv4/IPv6
family")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-01-17 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 0:25 BUG: corrupted list in nf_tables_commit syzbot
2020-01-17 4:45 ` syzbot [this message]
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=000000000000c31c6d059c4e9a6c@google.com \
--to=syzbot+37a6804945a3a13b1572@syzkaller.appspotmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=kadlec@netfilter.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).