From: syzbot ci <syzbot+ci1ee7eee4e49c2917@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: wifi: further RTNL redux
Date: Sun, 04 Oct 2026 14:24:44 -0700 [thread overview]
Message-ID: <6ac2c41c.9ad129c8.3858c0.0035.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] wifi: further RTNL redux
https://lore.kernel.org/all/20261004190122.1559001-20-johannes@sipsolutions.net
* [PATCH wireless-next 01/18] wifi: cfg80211: track netdev running state under wiphy mutex
* [PATCH wireless-next 02/18] wifi: nl80211: allow device lookup under RCU
* [PATCH wireless-next 03/18] wifi: nl80211: avoid rtnl for commands that don't want it
* [PATCH wireless-next 04/18] wifi: nl80211: don't take rtnl for most dumps
* [PATCH wireless-next 05/18] wifi: cfg80211: reg: update channels under wiphy mutex
* [PATCH wireless-next 06/18] wifi: cfg80211: reg: set intersected regd under wiphy mutex
* [PATCH wireless-next 07/18] wifi: cfg80211: update channel DFS data under wiphy mutex
* [PATCH wireless-next 08/18] wifi: mac80211_hwsim: call cfg80211 event with wiphy mutex
* [PATCH wireless-next 09/18] wifi: cfg80211: document wiphy mutex for radar/CAC events
* [PATCH wireless-next 10/18] wifi: cfg80211: add a mutex for regulatory/device list
* [PATCH wireless-next 11/18] wifi: cfg80211: allow walking wiphy list under cfg80211_mutex
* [PATCH wireless-next 12/18] wifi: ath: use freq_reg_info() under RCU
* [PATCH wireless-next 13/18] wifi: brcmsmac: use freq_reg_info() under RCU
* [PATCH wireless-next 14/18] wifi: rtlwifi: use freq_reg_info() under RCU
* [PATCH wireless-next 15/18] wifi: nl80211: read WMM reg rule under RCU
* [PATCH wireless-next 16/18] wifi: ath11k: read wiphy regd under RCU
* [PATCH wireless-next 17/18] wifi: ath12k: read wiphy regd under RCU
* [PATCH wireless-next 18/18] wifi: cfg80211: regulatory: stop using RTNL
and found the following issue:
SYZFATAL: image testing failed w/o kernel bug
Full report is available here:
https://ci.syzbot.org/series/0ddad86e-f612-4f74-9efc-50b8333a678f
***
SYZFATAL: image testing failed w/o kernel bug
tree: wireless-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/wireless/wireless-next.git
base: f49defea7668d8c68ec19fa085ef3da6075561c7
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/542e9d51-0d68-4eac-8303-1412498c7192/config
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[johannes.berg@intel.com johannes@sipsolutions.net linux-wireless@vger.kernel.org]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
next reply other threads:[~2026-10-04 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 21:24 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-10 20:44 [moderation/CI] Re: wifi: further RTNL redux syzbot ci
2026-10-10 21:14 ` Pimyn Girgis
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=6ac2c41c.9ad129c8.3858c0.0035.GAE@google.com \
--to=syzbot+ci1ee7eee4e49c2917@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.