From: syzbot <syzbot+1a797e1c81be78a2ace7@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com,
johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [wireless?] WARNING in __cfg80211_bss_update (2)
Date: Mon, 08 Jul 2024 17:36:21 -0700 [thread overview]
Message-ID: <0000000000000346a6061cc5b897@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: d270dd21bee0 Merge tag 'pci-v6.10-fixes-2' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=123cc8a5980000
kernel config: https://syzkaller.appspot.com/x/.config?x=864caee5f78cab51
dashboard link: https://syzkaller.appspot.com/bug?extid=1a797e1c81be78a2ace7
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/987e45087f46/disk-d270dd21.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/072b7b491dd1/vmlinux-d270dd21.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e0ddb6b56277/bzImage-d270dd21.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1a797e1c81be78a2ace7@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 19045 at net/wireless/scan.c:1714 cfg80211_combine_bsses net/wireless/scan.c:1714 [inline]
WARNING: CPU: 1 PID: 19045 at net/wireless/scan.c:1714 __cfg80211_bss_update+0x114a/0x20c0 net/wireless/scan.c:1954
Modules linked in:
CPU: 1 PID: 19045 Comm: kworker/u8:9 Not tainted 6.10.0-rc6-syzkaller-00210-gd270dd21bee0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:cfg80211_combine_bsses net/wireless/scan.c:1714 [inline]
RIP: 0010:__cfg80211_bss_update+0x114a/0x20c0 net/wireless/scan.c:1954
Code: e1 07 fe c1 38 c1 0f 8c 49 fb ff ff 48 8b 7c 24 68 e8 aa fb 26 f7 e9 3a fb ff ff e8 e0 46 c1 f6 90 0f 0b 90 e9 c0 fb ff ff 90 <0f> 0b 90 48 89 ef e8 9b 99 e1 f9 84 c0 0f 84 9f 00 00 00 e8 be 46
RSP: 0018:ffffc9000315ee98 EFLAGS: 00010206
RAX: ffff88806d6fec10 RBX: ffff88802b936488 RCX: dffffc0000000000
RDX: ffff88805e953c00 RSI: 0000000000000000 RDI: 0000000000000006
RBP: ffff88802b936410 R08: ffffffff8ad4de30 R09: 00000010fffff448
R10: 0000505050505050 R11: 0003000000000000 R12: ffff88802b936400
R13: 0000000000000000 R14: dffffc0000000000 R15: ffff88805ca01800
FS: 0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f00aee80836 CR3: 0000000021fd0000 CR4: 00000000003526f0
Call Trace:
<TASK>
cfg80211_inform_single_bss_data+0xfd6/0x2360 net/wireless/scan.c:2289
cfg80211_inform_bss_data+0x3dd/0x5a70 net/wireless/scan.c:3117
cfg80211_inform_bss_frame_data+0x3bc/0x720 net/wireless/scan.c:3207
ieee80211_bss_info_update+0x8a7/0xbc0 net/mac80211/scan.c:226
ieee80211_rx_bss_info net/mac80211/ibss.c:1099 [inline]
ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1578 [inline]
ieee80211_ibss_rx_queued_mgmt+0x1962/0x2d70 net/mac80211/ibss.c:1605
ieee80211_iface_process_skb net/mac80211/iface.c:1603 [inline]
ieee80211_iface_work+0x8a3/0xf10 net/mac80211/iface.c:1657
cfg80211_wiphy_work+0x221/0x260 net/wireless/core.c:437
process_one_work kernel/workqueue.c:3248 [inline]
process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3329
worker_thread+0x86d/0xd50 kernel/workqueue.c:3409
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-07-09 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 0:36 syzbot [this message]
2024-07-17 8:55 ` [syzbot] [wireless?] WARNING in __cfg80211_bss_update (2) 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=0000000000000346a6061cc5b897@google.com \
--to=syzbot+1a797e1c81be78a2ace7@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).