From: syzbot <syzbot+bfda097c12a00c8cae67@syzkaller.appspotmail.com>
To: andy@greyhouse.net, davem@davemloft.net, hdanton@sina.com,
j.vosburgh@gmail.com, jamie@nuviainc.com,
johannes.berg@intel.com, johannes@sipsolutions.net,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, vfalico@gmail.com
Subject: Re: WARNING in slave_kobj_release
Date: Wed, 17 Feb 2021 16:27:05 -0800 [thread overview]
Message-ID: <000000000000268f5d05bb91654a@google.com> (raw)
In-Reply-To: <000000000000064f0f05bb76ff3b@google.com>
syzbot has bisected this issue to:
commit dcd479e10a0510522a5d88b29b8f79ea3467d501
Author: Johannes Berg <johannes.berg@intel.com>
Date: Fri Oct 9 12:17:11 2020 +0000
mac80211: always wind down STA state
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=169ceb24d00000
start commit: f40ddce8 Linux 5.11
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=159ceb24d00000
console output: https://syzkaller.appspot.com/x/log.txt?x=119ceb24d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4b919ebed7b4902
dashboard link: https://syzkaller.appspot.com/bug?extid=bfda097c12a00c8cae67
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=111279f4d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15861a4cd00000
Reported-by: syzbot+bfda097c12a00c8cae67@syzkaller.appspotmail.com
Fixes: dcd479e10a05 ("mac80211: always wind down STA state")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-02-18 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 16:57 WARNING in slave_kobj_release syzbot
2021-02-18 0:27 ` 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=000000000000268f5d05bb91654a@google.com \
--to=syzbot+bfda097c12a00c8cae67@syzkaller.appspotmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=hdanton@sina.com \
--cc=j.vosburgh@gmail.com \
--cc=jamie@nuviainc.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vfalico@gmail.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).