Subject: [syzbot] [wireless?] WARNING in drv_unassign_vif_chanctx (2)

From: syzbot <[email-masked]>
Date: Sun, 29 Dec 2024 01:11:19 -0800

Hello,

syzbot found the following issue on:

HEAD commit:    9b2ffa6148b1 Merge tag 'mtd/fixes-for-6.13-rc5' of git://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12df6adf980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c078001e66e4a17e
dashboard link: https://syzkaller.appspot.com/bug?extid=25ce0caba1e325c6f224
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-9b2ffa61.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3bcb43c77ce7/vmlinux-9b2ffa61.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ef51b0b811d5/bzImage-9b2ffa61.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email-masked]

------------[ cut here ]------------
syzkaller0: Failed check-sdata-in-driver check, flags: 0x0
WARNING: CPU: 0 PID: 1134 at net/mac80211/driver-ops.c:360 drv_unassign_vif_chanctx+0x247/0x860 net/mac80211/driver-ops.c:360
Modules linked in:
CPU: 0 UID: 0 PID: 1134 Comm: kworker/u32:5 Not tainted 6.13.0-rc4-syzkaller-00012-g9b2ffa6148b1 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: netns cleanup_net
RIP: 0010:drv_unassign_vif_chanctx+0x247/0x860 net/mac80211/driver-ops.c:360
Code: 74 24 10 48 81 c6 20 01 00 00 48 89 74 24 10 e8 0f 4f 0c f7 8b 54 24 04 48 c7 c7 c0 fc 9d 8c 48 8b 74 24 10 e8 3a 15 cd f6 90 <0f> 0b 90 90 e8 f0 4e 0c f7 4c 89 ea 48 b8 00 00 00 00 00 fc ff df
RSP: 0018:ffffc9000677f5d8 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff88806a928d80 RCX: ffffffff815a1729
RDX: ffff888024f52440 RSI: ffffffff815a1736 RDI: 0000000000000001
RBP: ffff8880710e8e40 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000005 R12: ffff88806a92aa28
R13: ffff88806a929728 R14: ffff88806a92a9d0 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff88802b400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000569e04c0 CR3: 000000000db7e000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ieee80211_assign_link_chanctx+0x158/0xd80 net/mac80211/chan.c:885
 __ieee80211_link_release_channel+0x273/0x4b0 net/mac80211/chan.c:1859
 ieee80211_link_release_channel+0xda/0x1b0 net/mac80211/chan.c:2130
 unregister_netdevice_many_notify+0xf77/0x1e60 net/core/dev.c:11548
 unregister_netdevice_many net/core/dev.c:11590 [inline]
 unregister_netdevice_queue+0x307/0x3f0 net/core/dev.c:11462
 unregister_netdevice include/linux/netdevice.h:3192 [inline]
 _cfg80211_unregister_wdev+0x64b/0x830 net/wireless/core.c:1255
 ieee80211_remove_interfaces+0x36d/0x760 net/mac80211/iface.c:2307
 ieee80211_unregister_hw+0x55/0x3a0 net/mac80211/main.c:1671
 mac80211_hwsim_del_radio+0x268/0x370 drivers/net/wireless/virtual/mac80211_hwsim.c:5625
 hwsim_exit_net+0x33f/0x6d0 drivers/net/wireless/virtual/mac80211_hwsim.c:6505
 ops_exit_list+0xb0/0x180 net/core/net_namespace.c:172
 cleanup_net+0x5b7/0xbd0 net/core/net_namespace.c:648
 process_one_work+0x958/0x1b30 kernel/workqueue.c:3229
 process_scheduled_works kernel/workqueue.c:3310 [inline]
 worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391
 kthread+0x2c1/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at [email-masked].

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup