From: syzbot <syzbot+ef4ca92d9d6f5ba2f880@syzkaller.appspotmail.com>
To: davem@davemloft.net, expedicao@bandup.com.br, hdanton@sina.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, yuehaibing@huawei.com
Subject: Re: [syzbot] WARNING in sta_info_insert_rcu
Date: Sat, 06 Nov 2021 09:09:06 -0700 [thread overview]
Message-ID: <000000000000af312005d020fa29@google.com> (raw)
In-Reply-To: <0000000000004d87c705b00bcb0a@google.com>
syzbot suspects this issue was fixed by commit:
commit a6555f844549cd190eb060daef595f94d3de1582
Author: YueHaibing <yuehaibing@huawei.com>
Date: Fri Aug 27 14:42:30 2021 +0000
mac80211: Drop frames from invalid MAC address in ad-hoc mode
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=103db432b00000
start commit: 7266f2030eb0 Merge tag 'pm-5.13-rc8' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=533cb04fad26afdb
dashboard link: https://syzkaller.appspot.com/bug?extid=ef4ca92d9d6f5ba2f880
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11be2fd0300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10d85b14300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mac80211: Drop frames from invalid MAC address in ad-hoc mode
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-11-06 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 9:26 WARNING in sta_info_insert_rcu syzbot
2021-11-06 16:09 ` syzbot [this message]
2021-11-08 1:12 ` [syzbot] " YueHaibing
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=000000000000af312005d020fa29@google.com \
--to=syzbot+ef4ca92d9d6f5ba2f880@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=expedicao@bandup.com.br \
--cc=hdanton@sina.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=yuehaibing@huawei.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).