From: syzbot <syzbot+d4de7030f60c07837e60@syzkaller.appspotmail.com>
To: claudiajkang@gmail.com, davem@davemloft.net, edumazet@google.com,
ennoerlangen@gmail.com, george.mccollister@gmail.com,
hdanton@sina.com, johannes.berg@intel.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, nbd@nbd.name,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, toke@kernel.org
Subject: Re: [syzbot] WARNING: suspicious RCU usage in hsr_node_get_first
Date: Tue, 26 Jul 2022 15:46:07 -0700 [thread overview]
Message-ID: <000000000000edd28b05e4bd100b@google.com> (raw)
In-Reply-To: <000000000000beb14105dd852b6a@google.com>
syzbot suspects this issue was fixed by commit:
commit f856373e2f31ffd340e47e2b00027bd4070f74b3
Author: Felix Fietkau <nbd@nbd.name>
Date: Tue May 31 19:08:24 2022 +0000
wifi: mac80211: do not wake queues on a vif that is being stopped
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11100172080000
start commit: 0840a7914caa Merge tag 'char-misc-5.19-rc4' of git://git.k..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=542d3d75f0e6f36f
dashboard link: https://syzkaller.appspot.com/bug?extid=d4de7030f60c07837e60
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12820318080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11f144fff00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: wifi: mac80211: do not wake queues on a vif that is being stopped
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-07-26 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 2:08 [syzbot] WARNING: suspicious RCU usage in hsr_node_get_first syzbot
2022-07-26 22:46 ` 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=000000000000edd28b05e4bd100b@google.com \
--to=syzbot+d4de7030f60c07837e60@syzkaller.appspotmail.com \
--cc=claudiajkang@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ennoerlangen@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=hdanton@sina.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=toke@kernel.org \
/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).