WARNING in ieee80211_ibss_finish_sta

4 views
Skip to first unread message

syzbot

unread,
Jul 5, 2022, 2:14:21 AM7/5/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15443f38080000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=d46499641aa1508d7aa7
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d46499...@syzkaller.appspotmail.com

------------[ cut here ]------------
__do_sys_sendto net/socket.c:1911 [inline]
__se_sys_sendto net/socket.c:1907 [inline]
__x64_sys_sendto+0xdd/0x1b0 net/socket.c:1907
WARNING: CPU: 1 PID: 8677 at net/mac80211/sta_info.c:478 sta_info_insert_check net/mac80211/sta_info.c:478 [inline]
WARNING: CPU: 1 PID: 8677 at net/mac80211/sta_info.c:478 sta_info_insert_rcu.cold+0x29/0xd8 net/mac80211/sta_info.c:656
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
Kernel panic - not syncing: panic_on_warn set ...

entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fed83dc3ecc
Code: fa fa ff ff 44 8b 4c 24 2c 4c 8b 44 24 20 89 c5 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 34 89 ef 48 89 44 24 08 e8 20 fb ff ff 48 8b
RSP: 002b:00007fed82785000 EFLAGS: 00000293 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 00007fed827850f0 RCX: 00007fed83dc3ecc
RDX: 0000000000000020 RSI: 00007fed82785140 RDI: 0000000000000005
RBP: 0000000000000000 R08: 00007fed82785054 R09: 000000000000000c
R10: 0000000000000000 R11: 0000000000000293 R12: 00007fed827850a8
R13: 00007fed82785140 R14: 0000000000000005 R15: 0000000000000000
CPU: 1 PID: 8677 Comm: kworker/u4:2 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/29/2022
Workqueue: phy11 ieee80211_iface_work
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:sta_info_insert_check net/mac80211/sta_info.c:478 [inline]
RIP: 0010:sta_info_insert_rcu.cold+0x29/0xd8 net/mac80211/sta_info.c:656
Code: ff e8 46 36 4e f9 48 c7 c7 60 4b 67 89 e8 a5 67 df ff 0f 0b e9 4f ca 82 ff e8 2e 36 4e f9 48 c7 c7 60 4b 67 89 e8 8d 67 df ff <0f> 0b 41 bc ea ff ff ff e9 b9 db 82 ff e8 10 36 4e f9 48 c7 c7 60
RSP: 0018:ffff8880b3fdfa60 EFLAGS: 00010282
RAX: 0000000000000024 RBX: ffff88809bfee000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed10167fbf3e
RBP: 0000000000000001 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 00000000fdf3bcff
R13: ffff8880a17b8508 R14: ffff8880a17b84c0 R15: ffff88809df99bc0
ieee80211_ibss_finish_sta+0x25b/0x360 net/mac80211/ibss.c:601
ieee80211_ibss_work+0x2b6/0xe10 net/mac80211/ibss.c:1692
ieee80211_iface_work+0x7ba/0x8a0 net/mac80211/iface.c:1362
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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 syzk...@googlegroups.com.

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

syzbot

unread,
Nov 2, 2022, 2:14:30 AM11/2/22
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages