From: "Ömer Mete Kaya" <omermetekaya0@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: johannes@sipsolutions.net, kvalo@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ömer Mete Kaya" <omermetekaya0@gmail.com>,
syzbot+adeb8550754921fece20@syzkaller.appspotmail.com,
syzbot+101224300649c3eb8af4@syzkaller.appspotmail.com,
syzbot+8141dcbd23a8f857798a@syzkaller.appspotmail.com,
syzbot+b0ae8f1abf7d891e0426@syzkaller.appspotmail.com,
syzbot+d6bbe0f5705cb8a5aa2b@syzkaller.appspotmail.com
Subject: [PATCH v2] wifi: cfg80211: avoid holding rtnl_mutex across all cfg80211_leave() calls
Date: Thu, 3 Sep 2026 18:13:11 +0300 [thread overview]
Message-ID: <20260903151542.486376-2-omermetekaya0@gmail.com> (raw)
In-Reply-To: <20260903151542.486376-1-omermetekaya0@gmail.com>
reg_check_chans_work() holds rtnl_mutex for the entire duration of
iterating over all registered devices and calling cfg80211_leave() on
each invalid wdev. cfg80211_leave() can be slow (disconnect, stop AP,
leave mesh), causing rtnl_mutex starvation when many wireless interfaces
are present. This results in tasks waiting for rtnl_mutex for longer
than hung_task_timeout_secs:
INFO: task hung in inet_rtm_newaddr
INFO: task hung in inet6_rtm_newaddr
INFO: task hung in nsim_destroy
INFO: task hung in tun_chr_close
INFO: task hung in switchdev_deferred_process_work
Fix by walking cfg80211_rdev_list under RCU and acquiring rtnl per-device,
so other rtnl waiters get a chance to run between devices.
I could not add the Fixes: tag because this patch addresses five separate
hung task reports whose cause bisections all failed, making it impossible
to identify a single introducing commit.
Reported-by: syzbot+adeb8550754921fece20@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=adeb8550754921fece20
Reported-by: syzbot+101224300649c3eb8af4@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=101224300649c3eb8af4
Reported-by: syzbot+8141dcbd23a8f857798a@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=8141dcbd23a8f857798a
Reported-by: syzbot+b0ae8f1abf7d891e0426@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=b0ae8f1abf7d891e0426
Reported-by: syzbot+d6bbe0f5705cb8a5aa2b@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=d6bbe0f5705cb8a5aa2b
Signed-off-by: Ömer Mete Kaya <omermetekaya0@gmail.com>
---
net/wireless/reg.c | 19 ++++++++++++++-----
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/net/wireless/reg.c b/net/wireless/reg.c
index a8336baf85dc..a2e0d1cf8317 100644
--- a/net/wireless/reg.c
+++ b/net/wireless/reg.c
@@ -2466,12 +2466,21 @@ static void reg_check_chans_work(struct work_struct *work)
struct cfg80211_registered_device *rdev;
pr_debug("Verifying active interfaces after reg change\n");
- rtnl_lock();
-
- for_each_rdev(rdev)
+ /*
+ * Acquire rtnl per-device instead of holding it for the entire loop;
+ * cfg80211_leave() can be slow and starve other rtnl waiters otherwise.
+ * wiphy_unregister() holds rtnl across list_del_rcu() + synchronize_rcu(),
+ * so rdev cannot be freed while we hold rtnl_lock() below.
+ */
+ rcu_read_lock();
+ list_for_each_entry_rcu(rdev, &cfg80211_rdev_list, list) {
+ rcu_read_unlock();
+ rtnl_lock();
reg_leave_invalid_chans(&rdev->wiphy);
-
- rtnl_unlock();
+ rtnl_unlock();
+ rcu_read_lock();
+ }
+ rcu_read_unlock();
}
void reg_check_channels(void)
--
2.55.0
next prev parent reply other threads:[~2026-09-03 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 11:13 [PATCH] wifi: cfg80211: avoid holding rtnl_mutex across all cfg80211_leave() calls Ömer Mete Kaya
2026-09-03 15:13 ` Ömer Mete Kaya
2026-09-03 15:13 ` Ömer Mete Kaya [this message]
2026-09-05 18:45 ` [PATCH v2] " Simon Horman
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=20260903151542.486376-2-omermetekaya0@gmail.com \
--to=omermetekaya0@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+101224300649c3eb8af4@syzkaller.appspotmail.com \
--cc=syzbot+8141dcbd23a8f857798a@syzkaller.appspotmail.com \
--cc=syzbot+adeb8550754921fece20@syzkaller.appspotmail.com \
--cc=syzbot+b0ae8f1abf7d891e0426@syzkaller.appspotmail.com \
--cc=syzbot+d6bbe0f5705cb8a5aa2b@syzkaller.appspotmail.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