WARNING: possible circular locking dependency detected
6.14.0-rc5-syzkaller-00218-g2a520073e74f #0 Not tainted
------------------------------------------------------
kworker/u8:6/1107 is trying to acquire lock:

but task is already holding lock:
ffff888079180768 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: class_wiphy_constructor include/net/cfg80211.h:6061 [inline]
ffff888079180768 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: ieee80211_remove_interfaces+0xf1/0x720 net/mac80211/iface.c:2281

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:
-> #1 (&rdev->wiphy.mtx){+.+.}-{4:4}:
       __dev_open+0x2d4/0x540 net/core/dev.c:1635
-> #0 (team->team_lock_key){+.+.}-{4:4}:
other info that might help us debug this:


 *** DEADLOCK ***

stack backtrace:
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: netns cleanup_net
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2208