From: syzbot <syzbot+8bd4574e8c52c48c2595@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_tx_skb_tid
Date: Sun, 17 Aug 2025 14:16:29 -0700 [thread overview]
Message-ID: <68a246ad.050a0220.e29e5.0077.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 91325f31afc1 Merge tag 'mm-hotfixes-stable-2025-08-12-20-5..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11fecda2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=412ee2f8b704a5e6
dashboard link: https://syzkaller.appspot.com/bug?extid=8bd4574e8c52c48c2595
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/8c83f4baf60f/disk-91325f31.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/be959267627a/vmlinux-91325f31.xz
kernel image: https://storage.googleapis.com/syzbot-assets/68dffaf16c63/bzImage-91325f31.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8bd4574e8c52c48c2595@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 11866 at net/mac80211/tx.c:6202 ieee80211_tx_skb_tid+0x380/0x420 net/mac80211/tx.c:6202
Modules linked in:
CPU: 0 UID: 0 PID: 11866 Comm: syz.1.2132 Not tainted 6.17.0-rc1-syzkaller-00029-g91325f31afc1 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:ieee80211_tx_skb_tid+0x380/0x420 net/mac80211/tx.c:6202
Code: 9e a4 f6 e9 b1 fe ff ff e8 ed c3 c6 f6 90 0f 0b 90 e9 1f fe ff ff e8 df c3 c6 f6 90 0f 0b 90 e9 2a fe ff ff e8 d1 c3 c6 f6 90 <0f> 0b 90 e8 58 e2 fd ff 31 ff 48 8b 34 24 ba 02 00 00 00 48 83 c4
RSP: 0018:ffffc9000b697478 EFLAGS: 00010287
RAX: ffffffff8af8e7df RBX: ffffffff8af8e48f RCX: 0000000000080000
RDX: ffffc9000b7d9000 RSI: 000000000000298a RDI: 000000000000298b
RBP: 00000000ffffffff R08: 0000000000000000 R09: ffffffff8af8e48f
R10: dffffc0000000000 R11: ffffed100ebe1146 R12: ffff888054e94d80
R13: 0000000000000000 R14: 0000000000000001 R15: dffffc0000000000
FS: 00007f5035e4d6c0(0000) GS:ffff888125c1c000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f53e6e5ed58 CR3: 000000007d2fc000 CR4: 00000000003526f0
Call Trace:
<TASK>
ieee80211_tx_skb net/mac80211/ieee80211_i.h:2409 [inline]
mesh_plink_frame_tx+0x734/0xc10 net/mac80211/mesh_plink.c:354
mesh_plink_deactivate+0x18e/0x2f0 net/mac80211/mesh_plink.c:410
mesh_sta_cleanup+0x42/0x150 net/mac80211/mesh.c:171
__cleanup_single_sta net/mac80211/sta_info.c:167 [inline]
cleanup_single_sta+0x40f/0x660 net/mac80211/sta_info.c:192
__sta_info_flush+0x5e4/0x710 net/mac80211/sta_info.c:1683
sta_info_flush net/mac80211/sta_info.h:970 [inline]
ieee80211_do_stop+0x399/0x1fb0 net/mac80211/iface.c:509
ieee80211_stop+0x1b1/0x240 net/mac80211/iface.c:814
__dev_close_many+0x361/0x6f0 net/core/dev.c:1755
__dev_close net/core/dev.c:1767 [inline]
__dev_change_flags+0x2c7/0x6d0 net/core/dev.c:9530
netif_change_flags+0x88/0x1a0 net/core/dev.c:9595
dev_change_flags+0x130/0x260 net/core/dev_api.c:68
dev_ioctl+0x7b4/0x1150 net/core/dev_ioctl.c:824
sock_do_ioctl+0x22c/0x300 net/socket.c:1252
sock_ioctl+0x576/0x790 net/socket.c:1359
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:598 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:584
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f5034f8ebe9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5035e4d038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f50351b5fa0 RCX: 00007f5034f8ebe9
RDX: 0000200000000000 RSI: 0000000000008914 RDI: 0000000000000004
RBP: 00007f5035011e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f50351b6038 R14: 00007f50351b5fa0 R15: 00007f50352dfa28
</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
next reply other threads:[~2025-08-17 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 21:16 syzbot [this message]
2025-12-06 9:12 ` [syzbot] [wireless?] WARNING in ieee80211_tx_skb_tid syzbot
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=68a246ad.050a0220.e29e5.0077.GAE@google.com \
--to=syzbot+8bd4574e8c52c48c2595@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.