From: syzbot <syzbot+6446a589a5ca34dd6e8b@syzkaller.appspotmail.com>
To: davem@davemloft.net, eric.dumazet@gmail.com,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.von.dentz@intel.com, marcel@holtmann.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in l2cap_sock_getsockopt
Date: Mon, 17 Feb 2020 22:03:01 -0800 [thread overview]
Message-ID: <000000000000a98782059ed36cb4@google.com> (raw)
In-Reply-To: <0000000000007838f1059ed1cea5@google.com>
syzbot has bisected this bug to:
commit eab2404ba798a8efda2a970f44071c3406d94e57
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: Fri Feb 14 18:08:57 2020 +0000
Bluetooth: Add BT_PHY socket option
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b08045e00000
start commit: c25a951c Add linux-next specific files for 20200217
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=14708045e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=10708045e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=c727d8fc485ff049
dashboard link: https://syzkaller.appspot.com/bug?extid=6446a589a5ca34dd6e8b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10465579e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16dabb11e00000
Reported-by: syzbot+6446a589a5ca34dd6e8b@syzkaller.appspotmail.com
Fixes: eab2404ba798 ("Bluetooth: Add BT_PHY socket option")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-02-18 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 4:07 general protection fault in l2cap_sock_getsockopt syzbot
2020-02-18 5:43 ` Eric Dumazet
2020-02-18 6:03 ` 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=000000000000a98782059ed36cb4@google.com \
--to=syzbot+6446a589a5ca34dd6e8b@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox