From: syzbot <syzbot+0b4e1901856f4895db24@syzkaller.appspotmail.com>
To: davem@davemloft.net, johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in cfg80211_bss_update (2)
Date: Mon, 27 Sep 2021 00:19:24 -0700 [thread overview]
Message-ID: <000000000000aef88205ccf4ea41@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 428168f99517 Merge branch 'mlxsw-trap-adjacency'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=104c39d7300000
kernel config: https://syzkaller.appspot.com/x/.config?x=6d93fe4341f98704
dashboard link: https://syzkaller.appspot.com/bug?extid=0b4e1901856f4895db24
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
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+0b4e1901856f4895db24@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 26433 at net/wireless/scan.c:1574 cfg80211_combine_bsses net/wireless/scan.c:1574 [inline]
WARNING: CPU: 1 PID: 26433 at net/wireless/scan.c:1574 cfg80211_bss_update+0x19fe/0x2070 net/wireless/scan.c:1755
Modules linked in:
CPU: 1 PID: 26433 Comm: kworker/u4:10 Not tainted 5.15.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: phy15 ieee80211_iface_work
RIP: 0010:cfg80211_combine_bsses net/wireless/scan.c:1574 [inline]
RIP: 0010:cfg80211_bss_update+0x19fe/0x2070 net/wireless/scan.c:1755
Code: ff e9 e3 fd ff ff e8 71 37 0b f9 48 8d 7b 98 e8 c8 59 ff ff e9 46 fe ff ff e8 5e 37 0b f9 0f 0b e9 08 f2 ff ff e8 52 37 0b f9 <0f> 0b 4c 89 ff e8 88 99 72 fb 31 ff 89 c6 88 44 24 70 e8 7b 3d 0b
RSP: 0018:ffffc90004a7edc0 EFLAGS: 00010216
RAX: 0000000000001394 RBX: 0000000000000001 RCX: ffffc9000e290000
RDX: 0000000000040000 RSI: ffffffff886ad45e RDI: 0000000000000003
RBP: ffff888019e74400 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff886ac8f4 R11: 0000000000000000 R12: ffff888075a01468
R13: 0000000000000005 R14: ffff888075a01400 R15: ffff888019e74410
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000000 CR3: 000000001f5bb000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
cfg80211_inform_single_bss_frame_data+0x6e8/0xee0 net/wireless/scan.c:2411
cfg80211_inform_bss_frame_data+0xa7/0xb10 net/wireless/scan.c:2444
ieee80211_bss_info_update+0x376/0xb60 net/mac80211/scan.c:190
ieee80211_rx_bss_info net/mac80211/ibss.c:1119 [inline]
ieee80211_rx_mgmt_probe_beacon+0xcce/0x17c0 net/mac80211/ibss.c:1608
ieee80211_ibss_rx_queued_mgmt+0xd37/0x1610 net/mac80211/ibss.c:1635
ieee80211_iface_process_skb net/mac80211/iface.c:1439 [inline]
ieee80211_iface_work+0xa65/0xd00 net/mac80211/iface.c:1493
process_one_work+0x9bf/0x16b0 kernel/workqueue.c:2297
worker_thread+0x658/0x11f0 kernel/workqueue.c:2444
kthread+0x3e5/0x4d0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
---
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.
reply other threads:[~2021-09-27 7:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000aef88205ccf4ea41@google.com \
--to=syzbot+0b4e1901856f4895db24@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.