From: syzbot <syzbot+7bb955045fc0840decd3@syzkaller.appspotmail.com>
To: davem@davemloft.net, fweisbec@gmail.com, hdanton@sina.com,
johannes.berg@intel.com, johannes@sipsolutions.net,
kuba@kernel.org, kvalo@codeaurora.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
mingo@kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] INFO: rcu detected stall in ieee80211_tasklet_handler
Date: Tue, 26 Oct 2021 14:44:10 -0700 [thread overview]
Message-ID: <000000000000b6cfc405cf4860a7@google.com> (raw)
In-Reply-To: <00000000000058e2f605b6d2ad46@google.com>
syzbot suspects this issue was fixed by commit:
commit 313bbd1990b6ddfdaa7da098d0c56b098a833572
Author: Johannes Berg <johannes.berg@intel.com>
Date: Wed Sep 15 09:29:37 2021 +0000
mac80211-hwsim: fix late beacon hrtimer handling
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=151766bab00000
start commit: 835d31d319d9 Merge tag 'media/v5.15-1' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9c32e23fada3a0e4
dashboard link: https://syzkaller.appspot.com/bug?extid=7bb955045fc0840decd3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e08125300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b17dde300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mac80211-hwsim: fix late beacon hrtimer handling
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2021-10-26 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000058e2f605b6d2ad46@google.com>
2021-10-26 21:44 ` syzbot [this message]
2021-10-28 13:01 ` [syzbot] INFO: rcu detected stall in ieee80211_tasklet_handler Dmitry Vyukov
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=000000000000b6cfc405cf4860a7@google.com \
--to=syzbot+7bb955045fc0840decd3@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=hdanton@sina.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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).