[v6.1] WARNING in __cfg80211_connect_result

0 views
Skip to first unread message

syzbot

unread,
May 26, 2024, 6:05:30 PMMay 26
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 88690811da69 Linux 6.1.92
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1444dcd8980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee57a613e7f5bf6c
dashboard link: https://syzkaller.appspot.com/bug?extid=b1da1b7b278c35492b5b
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: https://storage.googleapis.com/syzbot-assets/a1bcd0657273/disk-88690811.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/46b8776e602b/vmlinux-88690811.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2b8c04da7a29/bzImage-88690811.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 102 at net/wireless/sme.c:839 __cfg80211_connect_result+0x1562/0x1f50
Modules linked in:
CPU: 0 PID: 102 Comm: kworker/u4:4 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Workqueue: cfg80211 cfg80211_event_work
RIP: 0010:__cfg80211_connect_result+0x1562/0x1f50 net/wireless/sme.c:839
Code: 00 e8 f2 74 94 00 89 c3 31 ff 89 c6 e8 b7 f7 93 f7 85 db 74 31 80 3d 92 f3 68 04 01 75 58 e8 45 f4 93 f7 eb 75 e8 3e f4 93 f7 <0f> 0b 4c 89 e7 4c 89 ee e8 71 21 00 00 e9 65 01 00 00 e8 27 f4 93
RSP: 0018:ffffc90001577a80 EFLAGS: 00010293
RAX: ffffffff89f69912 RBX: 0000000000000000 RCX: ffff8880136f1dc0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90001577ba0 R08: ffffffff89f69698 R09: fffffbfff2093851
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888059d42000
R13: ffff88802024d818 R14: 1ffff11004049b13 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c0001fc500 CR3: 000000000ce8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
cfg80211_process_wdev_events+0x238/0x4c0 net/wireless/util.c:971
cfg80211_process_rdev_events+0xa8/0x100 net/wireless/util.c:1012
cfg80211_event_work+0x2b/0x40 net/wireless/core.c:330
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</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 syzk...@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 all
Reply to author
Forward
0 new messages