[v5.15] WARNING in restore_regulatory_settings

0 views
Skip to first unread message

syzbot

unread,
Jul 2, 2023, 1:34:00 AM7/2/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4af60700a60c Linux 5.15.119
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=116a0458a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ba2032bf87adc4c7
dashboard link: https://syzkaller.appspot.com/bug?extid=11f6ba49d00a96f9d607
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5a37f09fce32/disk-4af60700.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/28ef8a07cc8f/vmlinux-4af60700.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ff6087a74939/bzImage-4af60700.xz

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

------------[ cut here ]------------
Unexpected user alpha2: �I
WARNING: CPU: 0 PID: 5400 at net/wireless/reg.c:439 is_user_regdom_saved net/wireless/reg.c:437 [inline]
WARNING: CPU: 0 PID: 5400 at net/wireless/reg.c:439 restore_alpha2 net/wireless/reg.c:3372 [inline]
WARNING: CPU: 0 PID: 5400 at net/wireless/reg.c:439 restore_regulatory_settings+0x3b4/0x2070 net/wireless/reg.c:3464
Modules linked in:
CPU: 0 PID: 5400 Comm: kworker/0:15 Not tainted 5.15.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Workqueue: events_power_efficient crda_timeout_work
RIP: 0010:is_user_regdom_saved net/wireless/reg.c:437 [inline]
RIP: 0010:restore_alpha2 net/wireless/reg.c:3372 [inline]
RIP: 0010:restore_regulatory_settings+0x3b4/0x2070 net/wireless/reg.c:3464
Code: 05 41 46 f0 07 88 44 24 1c e9 8e 01 00 00 e8 53 74 f3 f7 41 0f be f6 0f be 15 28 46 f0 07 48 c7 c7 40 f5 91 8b e8 5c 40 bf f7 <0f> 0b 4c 8b 35 53 43 31 04 4d 85 f6 0f 84 85 00 00 00 4c 89 f0 48
RSP: 0018:ffffc9000531fb40 EFLAGS: 00010246
RAX: ca005bbea9e70600 RBX: 0000000000000000 RCX: ffff88808dcbd940
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc9000531fc48 R08: ffffffff8166491c R09: ffffed1017344f24
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888022ca3628 R14: 00000000000000bf R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c0185bed6f CR3: 0000000085b97000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
crda_timeout_work+0x23/0x50 net/wireless/reg.c:539
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2307
worker_thread+0xaca/0x1280 kernel/workqueue.c:2454
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Jul 2, 2023, 7:08:52 AM7/2/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 4af60700a60c Linux 5.15.119
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1218c8a4a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ba2032bf87adc4c7
dashboard link: https://syzkaller.appspot.com/bug?extid=11f6ba49d00a96f9d607
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=147a9fd0a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=110809e7280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5a37f09fce32/disk-4af60700.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/28ef8a07cc8f/vmlinux-4af60700.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ff6087a74939/bzImage-4af60700.xz

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

------------[ cut here ]------------
Unexpected user alpha2: �I
WARNING: CPU: 1 PID: 21 at net/wireless/reg.c:439 is_user_regdom_saved net/wireless/reg.c:437 [inline]
WARNING: CPU: 1 PID: 21 at net/wireless/reg.c:439 restore_alpha2 net/wireless/reg.c:3372 [inline]
WARNING: CPU: 1 PID: 21 at net/wireless/reg.c:439 restore_regulatory_settings+0x3b4/0x2070 net/wireless/reg.c:3464
Modules linked in:
CPU: 1 PID: 21 Comm: kworker/1:0 Not tainted 5.15.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Workqueue: events_power_efficient crda_timeout_work
RIP: 0010:is_user_regdom_saved net/wireless/reg.c:437 [inline]
RIP: 0010:restore_alpha2 net/wireless/reg.c:3372 [inline]
RIP: 0010:restore_regulatory_settings+0x3b4/0x2070 net/wireless/reg.c:3464
Code: 05 41 46 f0 07 88 44 24 1c e9 8e 01 00 00 e8 53 74 f3 f7 41 0f be f6 0f be 15 28 46 f0 07 48 c7 c7 40 f5 91 8b e8 5c 40 bf f7 <0f> 0b 4c 8b 35 53 43 31 04 4d 85 f6 0f 84 85 00 00 00 4c 89 f0 48
RSP: 0018:ffffc90000db7b40 EFLAGS: 00010246
RAX: 651a7eb9aaaa3a00 RBX: 0000000000000000 RCX: ffff888012949dc0
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90000db7c48 R08: ffffffff8166491c R09: ffffed10173667a0
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88813fe1d128 R14: 00000000000000bf R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffee7b5c788 CR3: 00000000722c6000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
crda_timeout_work+0x23/0x50 net/wireless/reg.c:539
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2307
worker_thread+0xaca/0x1280 kernel/workqueue.c:2454
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

syzbot

unread,
Oct 10, 2023, 7:07:49 AM10/10/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages