[v5.15] WARNING in ieee80211_request_ibss_scan

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4735586da88e Linux 5.15.176
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16cbc218580000
kernel config: https://syzkaller.appspot.com/x/.config?x=caf0c22a63c5c861
dashboard link: https://syzkaller.appspot.com/bug?extid=ff9c38fbab99453919d5
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3e7a2d136136/disk-4735586d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7597375cf469/vmlinux-4735586d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/132474c9ad82/Image-4735586d.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ff9c38...@syzkaller.appspotmail.com

wlan1: Trigger new scan to find an IBSS to join
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1810 at net/mac80211/scan.c:1219 ieee80211_request_ibss_scan+0x588/0x604 net/mac80211/scan.c:1219
Modules linked in:
CPU: 0 PID: 1810 Comm: kworker/u4:7 Not tainted 5.15.176-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: phy12 ieee80211_iface_work
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ieee80211_request_ibss_scan+0x588/0x604 net/mac80211/scan.c:1219
lr : ieee80211_request_ibss_scan+0x588/0x604 net/mac80211/scan.c:1219
sp : ffff800024fe78a0
x29: ffff800024fe78e0 x28: ffff0000d7038e00 x27: 0000000000000005
x26: ffff0000d703aa40 x25: 0000000000000000 x24: dfff800000000000
x23: ffff0000d703d1b0 x22: 0000000000000001 x21: 0000000000000c80
x20: 1fffe0001ae071c0 x19: 0000000000000c80 x18: 0000000000000001
x17: 0000000000000000 x16: ffff8000084c43f0 x15: 00000000ffffffff
x14: 1ffff0000296c06c x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000cd5c0000
x8 : ffff8000114c1958 x7 : ffff8000114c1448 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000082e1c44
x2 : ffff0000cd5c0000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
ieee80211_request_ibss_scan+0x588/0x604 net/mac80211/scan.c:1219
ieee80211_sta_find_ibss net/mac80211/ibss.c:1507 [inline]
ieee80211_ibss_work+0xc6c/0x1230 net/mac80211/ibss.c:1710
ieee80211_iface_work+0x9d0/0xa80 net/mac80211/iface.c:1532
process_one_work+0x790/0x11b8 kernel/workqueue.c:2310
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
irq event stamp: 1661656
hardirqs last enabled at (1661655): [<ffff80000832c1a4>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (1661656): [<ffff800011b478f4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (1661652): [<ffff8000081b691c>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (1661652): [<ffff8000081b691c>] handle_softirqs+0xb88/0xdbc kernel/softirq.c:586
softirqs last disabled at (1661589): [<ffff8000081b6fb4>] __do_softirq kernel/softirq.c:592 [inline]
softirqs last disabled at (1661589): [<ffff8000081b6fb4>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (1661589): [<ffff8000081b6fb4>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (1661589): [<ffff8000081b6fb4>] __irq_exit_rcu+0x268/0x4d8 kernel/softirq.c:641
---[ end trace 0bf878402b9cd168 ]---


---
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.

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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.