[<prev] [next>] [day] [month] [year] [list]
Message-ID: <000000000000439664060b27c19b@google.com>
Date: Mon, 27 Nov 2023 12:00:34 -0800
From: syzbot <syzbot+9c67d243461f9800f17b@...kaller.appspotmail.com>
To: davem@...emloft.net, edumazet@...gle.com,
johannes@...solutions.net, kuba@...nel.org,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
netdev@...r.kernel.org, pabeni@...hat.com,
syzkaller-bugs@...glegroups.com
Subject: [syzbot] [wireless?] WARNING in __cfg80211_bss_update
Hello,
syzbot found the following issue on:
HEAD commit: 9b6de136b5f0 Merge tag 'loongarch-fixes-6.7-1' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=118a257ce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f2a9d08825f82ef3
dashboard link: https://syzkaller.appspot.com/bug?extid=9c67d243461f9800f17b
compiler: gcc (Debian 12.2.0-14) 12.2.0, 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/25ab52a5f324/disk-9b6de136.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/324f600af6eb/vmlinux-9b6de136.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7f3148d7c5fb/bzImage-9b6de136.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9c67d243461f9800f17b@...kaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1522 at net/wireless/scan.c:1692 cfg80211_combine_bsses net/wireless/scan.c:1692 [inline]
WARNING: CPU: 1 PID: 1522 at net/wireless/scan.c:1692 __cfg80211_bss_update+0x1cbc/0x24b0 net/wireless/scan.c:1877
Modules linked in:
CPU: 1 PID: 1522 Comm: kworker/u4:5 Not tainted 6.7.0-rc2-syzkaller-00029-g9b6de136b5f0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:cfg80211_combine_bsses net/wireless/scan.c:1692 [inline]
RIP: 0010:__cfg80211_bss_update+0x1cbc/0x24b0 net/wireless/scan.c:1877
Code: ff df 48 c1 ea 03 80 3c 02 00 0f 85 d5 02 00 00 48 b8 22 01 00 00 00 00 ad de 49 89 44 24 18 e9 02 f3 ff ff e8 05 21 b1 f7 90 <0f> 0b 90 e9 34 f0 ff ff e8 f7 20 b1 f7 48 8d 7b 98 e8 4e 73 ff ff
RSP: 0018:ffffc90005307568 EFLAGS: 00010283
RAX: 0000000000000ddf RBX: 0000000000000003 RCX: ffffc900146de000
RDX: 0000000000040000 RSI: ffffffff89d6692b RDI: 0000000000000000
RBP: ffff88807781e068 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000001 R11: 0000000000000000 R12: ffff88801ea9e800
R13: ffff88807781e000 R14: dffffc0000000000 R15: 0000000000000005
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b31723000 CR3: 000000002993c000 CR4: 0000000000350ef0
Call Trace:
<TASK>
cfg80211_inform_single_bss_frame_data+0x768/0xf30 net/wireless/scan.c:2905
cfg80211_inform_bss_frame_data+0xbf/0x290 net/wireless/scan.c:2936
ieee80211_bss_info_update+0x300/0x8f0 net/mac80211/scan.c:205
ieee80211_rx_bss_info net/mac80211/ibss.c:1098 [inline]
ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1577 [inline]
ieee80211_ibss_rx_queued_mgmt+0x1973/0x3120 net/mac80211/ibss.c:1604
ieee80211_iface_process_skb net/mac80211/iface.c:1589 [inline]
ieee80211_iface_work+0xa67/0xda0 net/mac80211/iface.c:1643
cfg80211_wiphy_work+0x24e/0x330 net/wireless/core.c:435
process_one_work+0x886/0x15d0 kernel/workqueue.c:2630
process_scheduled_works kernel/workqueue.c:2703 [inline]
worker_thread+0x8b9/0x1290 kernel/workqueue.c:2784
kthread+0x2c6/0x3a0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
</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@...glegroups.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
Powered by blists - more mailing lists