From: syzbot <syzbot+c3a167b5615df4ccd7fb@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: WARNING in ieee80211_start_next_roc
Date: Tue, 08 Dec 2020 18:03:11 -0800 [thread overview]
Message-ID: <00000000000015e0c705b5fe7627@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: e87297fa Merge tag 'drm-fixes-2020-12-04' of git://anongit..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17d9c9d3500000
kernel config: https://syzkaller.appspot.com/x/.config?x=e49433cfed49b7d9
dashboard link: https://syzkaller.appspot.com/bug?extid=c3a167b5615df4ccd7fb
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=171f77e3500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1603469b500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c3a167b5615df4ccd7fb@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 8533 at net/mac80211/offchannel.c:401 ieee80211_start_next_roc+0x1f4/0x240 net/mac80211/offchannel.c:401
Modules linked in:
CPU: 1 PID: 8533 Comm: kworker/u4:1 Not tainted 5.10.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: phy4 ieee80211_scan_work
RIP: 0010:ieee80211_start_next_roc+0x1f4/0x240 net/mac80211/offchannel.c:401
Code: d0 21 00 00 48 89 ef 48 89 c2 e8 77 7f 0b 00 5b 5d e9 d0 f4 28 f9 e8 cb f4 28 f9 48 89 ef e8 c3 73 ff ff eb 8d e8 bc f4 28 f9 <0f> 0b eb 84 48 c7 c7 9c df ec 8c e8 1c 73 6a f9 e9 2f fe ff ff e8
RSP: 0018:ffffc9000167fb80 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffffffff88470edd
RDX: ffff88801f861a40 RSI: ffffffff88470fc4 RDI: 0000000000000001
RBP: ffff8880292c0c80 R08: 0000000000000001 R09: ffffffff8ebaf727
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: dffffc0000000000 R14: 0000000000000001 R15: ffff8880292c25b8
FS: 0000000000000000(0000) GS:ffff8880b9f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff0e86f950 CR3: 000000001d954000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__ieee80211_scan_completed+0x602/0xed0 net/mac80211/scan.c:477
ieee80211_scan_work+0x3dd/0x1a90 net/mac80211/scan.c:1119
process_one_work+0x933/0x15a0 kernel/workqueue.c:2272
worker_thread+0x64c/0x1120 kernel/workqueue.c:2418
kthread+0x3b1/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2020-12-09 2:03 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=00000000000015e0c705b5fe7627@google.com \
--to=syzbot+c3a167b5615df4ccd7fb@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 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).