[v6.1] WARNING in restore_regulatory_settings (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6ae7ac5c4251 Linux 6.1.130
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16ab9874580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2d41f94f7752ee8c
dashboard link: https://syzkaller.appspot.com/bug?extid=69282f8bb1da578bb25e
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/e639f43a1070/disk-6ae7ac5c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eeca5786d4e2/vmlinux-6ae7ac5c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/17f18eb81c7f/Image-6ae7ac5c.gz.xz

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

------------[ cut here ]------------
Unexpected user alpha2: A�
WARNING: CPU: 0 PID: 6234 at net/wireless/reg.c:440 is_user_regdom_saved net/wireless/reg.c:438 [inline]
WARNING: CPU: 0 PID: 6234 at net/wireless/reg.c:440 restore_alpha2 net/wireless/reg.c:3432 [inline]
WARNING: CPU: 0 PID: 6234 at net/wireless/reg.c:440 restore_regulatory_settings+0x368/0x1b30 net/wireless/reg.c:3524
Modules linked in:
CPU: 0 PID: 6234 Comm: kworker/u4:13 Not tainted 6.1.130-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: events_power_efficient crda_timeout_work
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : is_user_regdom_saved net/wireless/reg.c:438 [inline]
pc : restore_alpha2 net/wireless/reg.c:3432 [inline]
pc : restore_regulatory_settings+0x368/0x1b30 net/wireless/reg.c:3524
lr : is_user_regdom_saved net/wireless/reg.c:438 [inline]
lr : restore_alpha2 net/wireless/reg.c:3432 [inline]
lr : restore_regulatory_settings+0x368/0x1b30 net/wireless/reg.c:3524
sp : ffff800022317a00
x29: ffff800022317af0 x28: ffff800022317aa8 x27: ffff800022317aa0
x26: ffff0000c2e0cc18 x25: ffff0000c2e0cc10 x24: 0000000000000000
x23: dfff800000000000 x22: 0000000000000041 x21: 0000000000000001
x20: 1ffff00004462f55 x19: ffff80001d1bb000 x18: ffff800022316e80
x17: 0000000000000000 x16: ffff80001232a73c x15: 0000000000000000
x14: 00000000ffffffff x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : 9cea56728d381a00
x8 : 9cea56728d381a00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff8000223172f8 x4 : ffff800015be5320 x3 : ffff800008588888
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000000
Call trace:
is_user_regdom_saved net/wireless/reg.c:438 [inline]
restore_alpha2 net/wireless/reg.c:3432 [inline]
restore_regulatory_settings+0x368/0x1b30 net/wireless/reg.c:3524
crda_timeout_work+0x38/0x68 net/wireless/reg.c:540
process_one_work+0x804/0x1484 kernel/workqueue.c:2292
worker_thread+0x8e4/0xfec kernel/workqueue.c:2439
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864
irq event stamp: 3137730
hardirqs last enabled at (3137729): [<ffff800008340490>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:261
hardirqs last disabled at (3137730): [<ffff80001232641c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (3137698): [<ffff8000120988d0>] spin_unlock_bh include/linux/spinlock.h:396 [inline]
softirqs last enabled at (3137698): [<ffff8000120988d0>] batadv_nc_purge_paths+0x2f4/0x378 net/batman-adv/network-coding.c:471
softirqs last disabled at (3137696): [<ffff8000120986ac>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (3137696): [<ffff8000120986ac>] batadv_nc_purge_paths+0xd0/0x378 net/batman-adv/network-coding.c:442
---[ end trace 0000000000000000 ]---


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