From: syzbot <syzbot+04851834dc894437cf21@syzkaller.appspotmail.com>
To: johannes@sipsolutions.net, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [wireless?] WARNING in ieee80211_teardown_sdata
Date: Tue, 05 Aug 2025 12:48:30 -0700 [thread overview]
Message-ID: <6892600e.050a0220.7f033.002f.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 89748acdf226 Merge tag 'drm-next-2025-08-01' of https://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1603e2a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8b51b56c81c0761d
dashboard link: https://syzkaller.appspot.com/bug?extid=04851834dc894437cf21
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/095171b2ab97/disk-89748acd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/48866e36b5ed/vmlinux-89748acd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/be4634873fa0/bzImage-89748acd.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+04851834dc894437cf21@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1161 at net/mac80211/iface.c:848 ieee80211_teardown_sdata+0xd2/0x140 net/mac80211/iface.c:848
Modules linked in:
CPU: 0 UID: 0 PID: 1161 Comm: kworker/u8:8 Not tainted 6.16.0-syzkaller-10499-g89748acdf226 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: netns cleanup_net
RIP: 0010:ieee80211_teardown_sdata+0xd2/0x140 net/mac80211/iface.c:848
Code: f6 48 89 df 31 f6 31 d2 e8 db 99 00 00 48 81 c3 80 17 00 00 48 89 df 5b 41 5c 41 5e 41 5f 5d e9 54 ba 00 00 e8 bf b6 d6 f6 90 <0f> 0b 90 4c 8d bb a0 09 00 00 4c 89 f8 48 c1 e8 03 42 80 3c 20 00
RSP: 0018:ffffc900040df390 EFLAGS: 00010293
RAX: ffffffff8ae8cce1 RBX: ffff888038ab8d80 RCX: ffff888027048000
RDX: 0000000000000000 RSI: 00000000ffffff9f RDI: ffff888038ab8d80
RBP: ffffc900040df530 R08: ffffffff8fa1ba37 R09: 1ffffffff1f43746
R10: dffffc0000000000 R11: ffffffff8ae92c70 R12: dffffc0000000000
R13: ffff888038ab8c10 R14: ffff888038ab9978 R15: ffff888038ab8000
FS: 0000000000000000(0000) GS:ffff888125c5b000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa038adcf98 CR3: 000000003edb8000 CR4: 0000000000350ef0
Call Trace:
<TASK>
unregister_netdevice_many_notify+0x1953/0x1ff0 net/core/dev.c:12177
unregister_netdevice_many net/core/dev.c:12219 [inline]
unregister_netdevice_queue+0x33c/0x380 net/core/dev.c:12063
unregister_netdevice include/linux/netdevice.h:3382 [inline]
_cfg80211_unregister_wdev+0x165/0x590 net/wireless/core.c:1275
ieee80211_remove_interfaces+0x49a/0x6d0 net/mac80211/iface.c:2391
ieee80211_unregister_hw+0x5d/0x2c0 net/mac80211/main.c:1664
mac80211_hwsim_del_radio+0x275/0x460 drivers/net/wireless/virtual/mac80211_hwsim.c:5674
hwsim_exit_net+0x584/0x640 drivers/net/wireless/virtual/mac80211_hwsim.c:6554
ops_exit_list net/core/net_namespace.c:198 [inline]
ops_undo_list+0x49a/0x990 net/core/net_namespace.c:251
cleanup_net+0x4c5/0x800 net/core/net_namespace.c:682
process_one_work kernel/workqueue.c:3236 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3319
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400
kthread+0x711/0x8a0 kernel/kthread.c:464
ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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 syzkaller@googlegroups.com.
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
reply other threads:[~2025-08-05 19:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6892600e.050a0220.7f033.002f.GAE@google.com \
--to=syzbot+04851834dc894437cf21@syzkaller.appspotmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@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.