From: syzbot <syzbot+b904439e05f11f81ac62@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
jhs@mojatatu.com, jiri@nvidia.com, johannes@sipsolutions.net,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, pctammela@mojatatu.com,
syzkaller-bugs@googlegroups.com, victor@mojatatu.com,
vladimir.oltean@nxp.com
Subject: Re: [syzbot] [net?] [wireless?] INFO: rcu detected stall in cfg80211_wiphy_work
Date: Sun, 08 Oct 2023 09:57:28 -0700 [thread overview]
Message-ID: <0000000000006278b30607375e8f@google.com> (raw)
In-Reply-To: <000000000000d730410602d76cf6@google.com>
syzbot suspects this issue was fixed by commit:
commit da71714e359b64bd7aab3bd56ec53f307f058133
Author: Jamal Hadi Salim <jhs@mojatatu.com>
Date: Tue Aug 22 10:12:31 2023 +0000
net/sched: fix a qdisc modification with ambiguous command request
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14e978e9680000
start commit: cacc6e22932f tpm: Add a helper for checking hwrng enabled
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=3e670757e16affb
dashboard link: https://syzkaller.appspot.com/bug?extid=b904439e05f11f81ac62
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14a49fcda80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=136f8679a80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net/sched: fix a qdisc modification with ambiguous command request
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-10-08 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 0:48 [syzbot] [net?] [wireless?] INFO: rcu detected stall in cfg80211_wiphy_work syzbot
2023-10-08 16:57 ` 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=0000000000006278b30607375e8f@google.com \
--to=syzbot+b904439e05f11f81ac62@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jhs@mojatatu.com \
--cc=jiri@nvidia.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=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=victor@mojatatu.com \
--cc=vladimir.oltean@nxp.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).