[v5.15] WARNING in __cfg80211_connect_result

0 views
Skip to first unread message

syzbot

unread,
Jun 14, 2024, 8:59:22 PM (12 days ago) Jun 14
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c61bd26ae81a Linux 5.15.160
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=174b477a980000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a313cb27403a960
dashboard link: https://syzkaller.appspot.com/bug?extid=82dd66674b8a7090fdb1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c5c43c69147f/disk-c61bd26a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3e9c98d00e66/vmlinux-c61bd26a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e9da759b078f/Image-c61bd26a.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 985 at net/wireless/sme.c:768 __cfg80211_connect_result+0xc70/0x1004 net/wireless/sme.c:768
Modules linked in:
CPU: 0 PID: 985 Comm: kworker/u4:4 Not tainted 5.15.160-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Workqueue: cfg80211 cfg80211_event_work
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __cfg80211_connect_result+0xc70/0x1004 net/wireless/sme.c:768
lr : __cfg80211_connect_result+0xc70/0x1004 net/wireless/sme.c:768
sp : ffff80001de879a0
x29: ffff80001de87a30 x28: 1fffe00019f48c00 x27: 1fffe00019f48c38
x26: 1ffff00003bd0f38 x25: dfff800000000000 x24: 1fffe0001b6cc7c5
x23: ffff0000cfa460e2 x22: ffff0000cfa461c0 x21: 0000000000000000
x20: ffff0000db663e28 x19: ffff0000cfa46000 x18: 0000000000000201
x17: 0000000000000000 x16: ffff8000084c430c x15: 0000000000000003
x14: ffff0000c8791b40 x13: 0000000000ff0100 x12: 0000000000000003
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000c8791b40
x8 : ffff8000112390d4 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff80000804685c
x2 : 0000000000000006 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
__cfg80211_connect_result+0xc70/0x1004 net/wireless/sme.c:768
cfg80211_process_wdev_events+0x1f8/0x450 net/wireless/util.c:965
cfg80211_process_rdev_events+0xc8/0x12c net/wireless/util.c:1006
cfg80211_event_work+0x34/0x4c net/wireless/core.c:330
process_one_work+0x790/0x11b8 kernel/workqueue.c:2310
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
irq event stamp: 708832
hardirqs last enabled at (708831): [<ffff8000081b5d1c>] __local_bh_enable_ip+0x230/0x470 kernel/softirq.c:388
hardirqs last disabled at (708832): [<ffff800011997b20>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (708830): [<ffff800011187b04>] spin_unlock_bh include/linux/spinlock.h:408 [inline]
softirqs last enabled at (708830): [<ffff800011187b04>] cfg80211_get_bss+0x6e4/0xd10 net/wireless/scan.c:1512
softirqs last disabled at (708828): [<ffff800011187544>] spin_lock_bh include/linux/spinlock.h:368 [inline]
softirqs last disabled at (708828): [<ffff800011187544>] cfg80211_get_bss+0x124/0xd10 net/wireless/scan.c:1486
---[ end trace 279680603ae4656a ]---


---
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

syzbot

unread,
Jun 22, 2024, 3:41:24 PM (4 days ago) Jun 22
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 4878aadf2d15 Linux 5.15.161
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13dccd46980000
kernel config: https://syzkaller.appspot.com/x/.config?x=875d98826c53bf16
dashboard link: https://syzkaller.appspot.com/bug?extid=82dd66674b8a7090fdb1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=145f77ee980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=158ef741980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f227a150ea92/disk-4878aadf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6cfc50bf8b4e/vmlinux-4878aadf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23f7adc3c761/bzImage-4878aadf.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 300 at net/wireless/sme.c:768 __cfg80211_connect_result+0xe2e/0x10b0
Modules linked in:
CPU: 0 PID: 300 Comm: kworker/u4:3 Not tainted 5.15.161-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Workqueue: cfg80211 cfg80211_event_work
RIP: 0010:__cfg80211_connect_result+0xe2e/0x10b0 net/wireless/sme.c:768
Code: ff e8 b6 a0 e4 f7 0f 0b e9 35 f7 ff ff e8 aa a0 e4 f7 0f 0b e9 95 f7 ff ff e8 9e a0 e4 f7 0f 0b e9 f9 f8 ff ff e8 92 a0 e4 f7 <0f> 0b e9 4a ff ff ff e8 86 a0 e4 f7 0f 0b e9 49 fa ff ff e8 7a a0
RSP: 0018:ffffc90002e87ac0 EFLAGS: 00010293
RAX: ffffffff899bba3e RBX: 0000000000000000 RCX: ffff888018a4d940
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90002e87ba0 R08: ffffffff899bb23e R09: fffffbfff1f7f226
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880779691c0
R13: ffff888012b19528 R14: dffffc0000000000 R15: 1ffff1100ef2d238
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007faf8b5a22d0 CR3: 0000000022f11000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
cfg80211_process_wdev_events+0x238/0x4c0 net/wireless/util.c:965
cfg80211_process_rdev_events+0xa8/0x100 net/wireless/util.c:1006
cfg80211_event_work+0x2b/0x40 net/wireless/core.c:330
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
</TASK>


---
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.
Reply all
Reply to author
Forward
0 new messages