From: syzbot <syzbot+e8a797964a4180eb57d5@syzkaller.appspotmail.com>
To: astrachan@google.com, davem@davemloft.net, ghartman@google.com,
johannes.berg@intel.com, johannes@sipsolutions.net,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
muntsinger@google.com, netdev@vger.kernel.org,
schuffelen@google.com, syzkaller-bugs@googlegroups.com
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in cfg80211_wext_siwfrag
Date: Tue, 07 Jan 2020 02:12:01 -0800 [thread overview]
Message-ID: <000000000000cb3c3c059b8a01e3@google.com> (raw)
In-Reply-To: <0000000000004ceb27059b868b57@google.com>
syzbot has bisected this bug to:
commit c7cdba31ed8b87526db978976392802d3f93110c
Author: Cody Schuffelen <schuffelen@google.com>
Date: Wed Nov 21 03:14:49 2018 +0000
mac80211-next: rtnetlink wifi simulation device
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11cf6885e00000
start commit: d89091a4 macb: Don't unregister clks unconditionally
git tree: net
final crash: https://syzkaller.appspot.com/x/report.txt?x=13cf6885e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15cf6885e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=f2f3ef188b7e16cf
dashboard link: https://syzkaller.appspot.com/bug?extid=e8a797964a4180eb57d5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c85915e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11c02bc1e00000
Reported-by: syzbot+e8a797964a4180eb57d5@syzkaller.appspotmail.com
Fixes: c7cdba31ed8b ("mac80211-next: rtnetlink wifi simulation device")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-01-07 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 6:04 BUG: unable to handle kernel NULL pointer dereference in cfg80211_wext_siwfrag syzbot
2020-01-07 10:12 ` 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=000000000000cb3c3c059b8a01e3@google.com \
--to=syzbot+e8a797964a4180eb57d5@syzkaller.appspotmail.com \
--cc=astrachan@google.com \
--cc=davem@davemloft.net \
--cc=ghartman@google.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=muntsinger@google.com \
--cc=netdev@vger.kernel.org \
--cc=schuffelen@google.com \
--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;
as well as URLs for NNTP newsgroup(s).