From: syzbot <syzbot+0bef568258653cff272f@syzkaller.appspotmail.com>
To: a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
davem@davemloft.net, geert@linux-m68k.org,
javier@osg.samsung.com, johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@armlinux.org.uk, marcel@holtmann.org,
mareklindner@neomailbox.ch, netdev@vger.kernel.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in hci_event_packet
Date: Tue, 04 Aug 2020 06:01:06 -0700 [thread overview]
Message-ID: <0000000000002da68705ac0cd9ab@google.com> (raw)
In-Reply-To: <000000000000a7eb5e05abeb197d@google.com>
syzbot has bisected this issue to:
commit 941992d2944789641470626e9336d663236b1d28
Author: Javier Martinez Canillas <javier@osg.samsung.com>
Date: Mon Sep 12 14:03:34 2016 +0000
ethernet: amd: use IS_ENABLED() instead of checking for built-in or module
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=155180c2900000
start commit: bcf87687 Linux 5.8
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=175180c2900000
console output: https://syzkaller.appspot.com/x/log.txt?x=135180c2900000
kernel config: https://syzkaller.appspot.com/x/.config?x=4b489d75d0c8859d
dashboard link: https://syzkaller.appspot.com/bug?extid=0bef568258653cff272f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1043af04900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12ca1dea900000
Reported-by: syzbot+0bef568258653cff272f@syzkaller.appspotmail.com
Fixes: 941992d29447 ("ethernet: amd: use IS_ENABLED() instead of checking for built-in or module")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-08-04 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 20:45 general protection fault in hci_event_packet syzbot
2020-08-04 13:01 ` 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=0000000000002da68705ac0cd9ab@google.com \
--to=syzbot+0bef568258653cff272f@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=javier@osg.samsung.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcel@holtmann.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=sw@simonwunderlich.de \
--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.