From: syzbot <syzbot+d979bd35c8a76fd1b6f5@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?] BUG: using smp_processor_id() in preemptible code in ieee80211_tx_control_port
Date: Wed, 09 Sep 2026 15:44:46 -0700 [thread overview]
Message-ID: <6aa1e15e.f81106d8.2ab401.0003.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: a9d7ced84989 Add linux-next specific files for 20260908
git tree: linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=149cfaf9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=17eeb09695a2b3c9
dashboard link: https://syzkaller.appspot.com/bug?extid=d979bd35c8a76fd1b6f5
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=129cfaf9580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=139866f9580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4f470407358e/disk-a9d7ced8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/858b9d7ba687/vmlinux-a9d7ced8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ef971d22d75f/bzImage-a9d7ced8.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d979bd35c8a76fd1b6f5@syzkaller.appspotmail.com
BUG: using smp_processor_id() in preemptible [00000000] code: syz-executor240/5639
caller is dev_sw_netstats_tx_add include/linux/netdevice.h:3086 [inline]
caller is ieee80211_tx_control_port+0xac7/0x1100 net/mac80211/tx.c:6656
CPU: 0 UID: 0 PID: 5639 Comm: syz-executor240 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
check_preemption_disabled+0xcd/0xd0 lib/smp_processor_id.c:47
dev_sw_netstats_tx_add include/linux/netdevice.h:3086 [inline]
ieee80211_tx_control_port+0xac7/0x1100 net/mac80211/tx.c:6656
rdev_tx_control_port net/wireless/rdev-ops.h:783 [inline]
nl80211_tx_control_port+0x624/0x960 net/wireless/nl80211.c:18603
genl_family_rcv_msg_doit+0x233/0x340 net/netlink/genetlink.c:1114
genl_family_rcv_msg net/netlink/genetlink.c:1194 [inline]
genl_rcv_msg+0x614/0x7a0 net/netlink/genetlink.c:1209
netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2556
genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218
netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
netlink_unicast+0x7bd/0x940 net/netlink/af_netlink.c:1345
netlink_sendmsg+0x7c3/0xae0 net/netlink/af_netlink.c:1900
sock_sendmsg_nosec+0x13a/0x180 net/socket.c:800
__sock_sendmsg net/socket.c:815 [inline]
____sys_sendmsg+0x54e/0x850 net/socket.c:2713
___sys_sendmsg+0x2a5/0x360 net/socket.c:2767
__sys_sendmsg net/socket.c:2799 [inline]
__do_sys_sendmsg net/socket.c:2804 [inline]
__se_sys_sendmsg net/socket.c:2802 [inline]
__x64_sys_sendmsg+0x1b1/0x290 net/socket.c:2802
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2fe280ba69
Code: c0 79 93 eb d5 48 8d 7c 1d 00 eb 99 0f 1f 44 00 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 d0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc9ac26a08 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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:[~2026-09-09 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 22:44 syzbot [this message]
2026-09-10 4:07 ` Forwarded: [PATCH] mac80211: fix using smp_processor_id() in preemptible code in ieee80211_tx_control_port() syzbot
[not found] <20260910040733.22352-1-kartikey406@gmail.com>
2026-09-10 5:37 ` [syzbot] [wireless?] BUG: using smp_processor_id() in preemptible code in ieee80211_tx_control_port 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=6aa1e15e.f81106d8.2ab401.0003.GAE@google.com \
--to=syzbot+d979bd35c8a76fd1b6f5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®