[syzbot] WARNING in cfg80211_ch_switch_notify

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 34d1d36073ea Add linux-next specific files for 20220621
git tree: linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=175aca1ff00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b24b62d1c051cfc8
dashboard link: https://syzkaller.appspot.com/bug?extid=90d912872157e63589e4
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a50e1ff00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=104b1cc4080000

The issue was bisected to:

commit 7b0a0e3c3a88260b6fcb017e49f198463aa62ed1
Author: Johannes Berg <johann...@intel.com>
Date: Thu Apr 14 14:50:57 2022 +0000

wifi: cfg80211: do some rework towards MLO link APIs

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=177e008ff00000
final oops: https://syzkaller.appspot.com/x/report.txt?x=14fe008ff00000
console output: https://syzkaller.appspot.com/x/log.txt?x=10fe008ff00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+90d912...@syzkaller.appspotmail.com
Fixes: 7b0a0e3c3a88 ("wifi: cfg80211: do some rework towards MLO link APIs")

------------[ cut here ]------------
WARNING: CPU: 1 PID: 1021 at net/wireless/nl80211.c:18562 cfg80211_ch_switch_notify+0x3b7/0x8a0 net/wireless/nl80211.c:18562
Modules linked in:
CPU: 1 PID: 1021 Comm: kworker/u4:5 Not tainted 5.19.0-rc3-next-20220621-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: phy4 ieee80211_csa_finalize_work

RIP: 0010:cfg80211_ch_switch_notify+0x3b7/0x8a0 net/wireless/nl80211.c:18562
Code: fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 d2 04 00 00 49 8b 14 24 44 89 ee 48 89 ef e8 33 fa fb ff e9 44 ff ff ff e8 e9 78 cc f8 <0f> 0b e9 38 ff ff ff e8 dd 78 cc f8 48 8d bd f8 04 00 00 48 ba 00
RSP: 0018:ffffc90004dcfc60 EFLAGS: 00010293

RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffff88801eea57c0 RSI: ffffffff88ae4467 RDI: 0000000000000005
RBP: ffff88801f004c90 R08: 0000000000000005 R09: 0000000000000009
R10: 0000000000000001 R11: 0000000000000010 R12: ffff88801f006458
R13: 0000000000000000 R14: ffff88801f004000 R15: ffff888021d90000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000021000000 CR3: 000000000ba8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__ieee80211_csa_finalize+0x738/0xc90 net/mac80211/cfg.c:3432
ieee80211_csa_finalize net/mac80211/cfg.c:3439 [inline]
ieee80211_csa_finalize_work+0x131/0x170 net/mac80211/cfg.c:3464
process_one_work+0x996/0x1610 kernel/workqueue.c:2289
worker_thread+0x665/0x1080 kernel/workqueue.c:2436
kthread+0x2e9/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:302
</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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches