From: syzbot <syzbot+437bf61d165c87bd40fb@syzkaller.appspotmail.com>
To: coreteam@netfilter.org, davem@davemloft.net, fw@strlen.de,
johan.hedberg@gmail.com, kadlec@netfilter.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, max.chou@realtek.com,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pablo@netfilter.org, syzkaller-bugs@googlegroups.com
Subject: Re: BUG: corrupted list in __nf_tables_abort
Date: Sat, 14 Mar 2020 16:29:02 -0700 [thread overview]
Message-ID: <0000000000007f2c5b05a0d8f312@google.com> (raw)
In-Reply-To: <0000000000001ba488059c65d352@google.com>
syzbot suspects this bug was fixed by commit:
commit 34682110abc50ffea7e002b0c2fd7ea9e0000ccc
Author: Max Chou <max.chou@realtek.com>
Date: Wed Nov 27 03:01:07 2019 +0000
Bluetooth: btusb: Edit the logical value for Realtek Bluetooth reset
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=113e9919e00000
start commit: d5d359b0 Merge branch 'for-linus' of git://git.kernel.org/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=83c00afca9cf5153
dashboard link: https://syzkaller.appspot.com/bug?extid=437bf61d165c87bd40fb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=168a1611e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=162f0376e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: Bluetooth: btusb: Edit the logical value for Realtek Bluetooth reset
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-03-15 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 8:27 BUG: corrupted list in __nf_tables_abort syzbot
2020-01-18 13:18 ` syzbot
2020-03-14 23:29 ` syzbot [this message]
2020-03-15 0:18 ` 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=0000000000007f2c5b05a0d8f312@google.com \
--to=syzbot+437bf61d165c87bd40fb@syzkaller.appspotmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=johan.hedberg@gmail.com \
--cc=kadlec@netfilter.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.