From: syzbot <syzbot+6ca99af7e70e298bd09d@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 nft_obj_del
Date: Wed, 15 Jan 2020 22:03:00 -0800 [thread overview]
Message-ID: <000000000000d7aad9059c3b93b7@google.com> (raw)
In-Reply-To: <000000000000bc757e059c36db18@google.com>
syzbot has bisected this bug to:
commit 20651cefd25ffa77a15cab5853b175a6dc975ec2
Author: Florian Westphal <fw@strlen•de>
Date: Tue Jan 9 13:30:48 2018 +0000
netfilter: x_tables: unbreak module auto loading
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1073a33ee00000
start commit: 8b792f84 Merge branch 'mlxsw-Various-fixes'
git tree: net
final crash: https://syzkaller.appspot.com/x/report.txt?x=1273a33ee00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1473a33ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e89bd00623fe71e
dashboard link: https://syzkaller.appspot.com/bug?extid=6ca99af7e70e298bd09d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=168b95e1e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f29b3ee00000
Reported-by: syzbot+6ca99af7e70e298bd09d@syzkaller•appspotmail.com
Fixes: 20651cefd25f ("netfilter: x_tables: unbreak module auto loading")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-01-16 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 0:25 BUG: corrupted list in nft_obj_del syzbot
2020-01-16 6:03 ` syzbot [this message]
2020-01-16 14:53 ` 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=000000000000d7aad9059c3b93b7@google.com \
--to=syzbot+6ca99af7e70e298bd09d@syzkaller$(echo .)appspotmail.com \
--cc=coreteam@netfilter$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=fw@strlen$(echo .)de \
--cc=kadlec@blackhole$(echo .)kfki.hu \
--cc=kadlec@netfilter$(echo .)org \
--cc=kuznet@ms2$(echo .)inr.ac.ru \
--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 \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/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