From: syzbot <syzbot+4a38d3795200fd59a9eb@syzkaller•appspotmail.com>
To: davem@davemloft•net, 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 sco_sock_getsockopt
Date: Tue, 18 Feb 2020 05:37:02 -0800 [thread overview]
Message-ID: <0000000000005a9ed2059ed9c426@google.com> (raw)
In-Reply-To: <000000000000b7ee04059ed40af8@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=105f1a29e00000
start commit: c25a951c Add linux-next specific files for 20200217
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=125f1a29e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=145f1a29e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=c727d8fc485ff049
dashboard link: https://syzkaller.appspot.com/bug?extid=4a38d3795200fd59a9eb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=158849e9e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10e3d711e00000
Reported-by: syzbot+4a38d3795200fd59a9eb@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 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 6:47 general protection fault in sco_sock_getsockopt syzbot
2020-02-18 13:37 ` 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=0000000000005a9ed2059ed9c426@google.com \
--to=syzbot+4a38d3795200fd59a9eb@syzkaller$(echo .)appspotmail.com \
--cc=davem@davemloft$(echo .)net \
--cc=johan.hedberg@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-bluetooth@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=luiz.von.dentz@intel$(echo .)com \
--cc=marcel@holtmann$(echo .)org \
--cc=netdev@vger$(echo .)kernel.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