From: syzbot <syzbot+8b512026a7ec10dcbdd9@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 sta_info_insert_rcu (4)
Date: Mon, 18 Nov 2024 08:56:28 -0800 [thread overview]
Message-ID: <673b71bc.050a0220.87769.004d.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 0a9b9d17f3a7 Merge tag 'pm-6.12-rc8' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=179ef4c0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d2aeec8c0b2e420c
dashboard link: https://syzkaller.appspot.com/bug?extid=8b512026a7ec10dcbdd9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
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-0a9b9d17.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b80dd0292210/vmlinux-0a9b9d17.xz
kernel image: https://storage.googleapis.com/syzbot-assets/42a07c5c6678/bzImage-0a9b9d17.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8b512026a7ec10dcbdd9@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1025 at net/mac80211/sta_info.c:738 sta_info_insert_check net/mac80211/sta_info.c:737 [inline]
WARNING: CPU: 0 PID: 1025 at net/mac80211/sta_info.c:738 sta_info_insert_rcu+0x322/0x1900 net/mac80211/sta_info.c:942
Modules linked in:
CPU: 0 UID: 0 PID: 1025 Comm: kworker/u4:4 Not tainted 6.12.0-rc7-syzkaller-00070-g0a9b9d17f3a7 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:sta_info_insert_check net/mac80211/sta_info.c:737 [inline]
RIP: 0010:sta_info_insert_rcu+0x322/0x1900 net/mac80211/sta_info.c:942
Code: 85 db 4c 8b 6c 24 28 0f 84 90 00 00 00 e8 16 6e 4a f6 84 c0 0f 84 b4 00 00 00 e8 b9 80 64 f6 e9 0d 01 00 00 e8 af 80 64 f6 90 <0f> 0b 90 41 be ea ff ff ff 4c 8b 6c 24 28 4c 89 ee e8 98 d0 ff ff
RSP: 0018:ffffc9000227f9c0 EFLAGS: 00010293
RAX: ffffffff8b306961 RBX: 0000000000000001 RCX: ffff88803581a440
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: 00000000ffffffff R08: ffffffff8b3068ee R09: 1ffff11009fc6ace
R10: dffffc0000000000 R11: ffffed1009fc6acf R12: 00000000ffeeffff
R13: 000000000000ffff R14: 000000000000feff R15: ffff88804fe34cc0
FS: 0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fca30a06fb8 CR3: 00000000363e4000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ieee80211_ocb_finish_sta net/mac80211/ocb.c:102 [inline]
ieee80211_ocb_work+0x2fd/0x550 net/mac80211/ocb.c:136
cfg80211_wiphy_work+0x2db/0x490 net/wireless/core.c:440
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
worker_thread+0x870/0xd30 kernel/workqueue.c:3391
kthread+0x2f0/0x390 kernel/kthread.c:389
ret_from_fork+0x4b/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 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:[~2024-11-18 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 16:56 syzbot [this message]
2025-01-16 9:35 ` [syzbot] [wireless?] WARNING in sta_info_insert_rcu (4) syzbot
2025-06-16 13:40 ` [syzbot] [PATCH] wifi: mac80211: drop invalid source address OCB frames syzbot
2025-06-16 15:18 ` [syzbot] [PATCH wireless v2] " syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-06-16 13:40 [PATCH] " Johannes Berg
2025-06-16 14:02 ` [syzbot] [wireless?] WARNING in sta_info_insert_rcu (4) syzbot
2025-06-16 15:18 [PATCH wireless v2] wifi: mac80211: drop invalid source address OCB frames Johannes Berg
2025-06-16 15:45 ` [syzbot] [wireless?] WARNING in sta_info_insert_rcu (4) 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=673b71bc.050a0220.87769.004d.GAE@google.com \
--to=syzbot+8b512026a7ec10dcbdd9@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.