linux-kernel - [syzbot] [wireless?] WARNING in restore_regulatory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000000000001432c105ffcae455@google.com>
Date:   Wed, 05 Jul 2023 22:35:58 -0700
From:   syzbot <syzbot+dfe2fbeb4e710bbaddf9@...kaller.appspotmail.com>
To:     axboe@...nel.dk, brauner@...nel.org, davem@...emloft.net,
        edumazet@...gle.com, hare@...e.de, hch@....de,
        johannes@...solutions.net, kuba@...nel.org,
        linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
        netdev@...r.kernel.org, pabeni@...hat.com,
        syzkaller-bugs@...glegroups.com
Subject: [syzbot] [wireless?] WARNING in restore_regulatory_settings (2)

Hello,

syzbot found the following issue on:

HEAD commit:    6352a698ca5b Add linux-next specific files for 20230630
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11f564a4a80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=39b764f3018462fe
dashboard link: https://syzkaller.appspot.com/bug?extid=dfe2fbeb4e710bbaddf9
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=1640f4a0a80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11a10c40a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/55254daea013/disk-6352a698.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cb343779c938/vmlinux-6352a698.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3d451333dab6/bzImage-6352a698.xz

The issue was bisected to:

commit ae220766d87cd6799dbf918fea10613ae14c0654
Author: Christoph Hellwig <hch@....de>
Date:   Thu Jun 8 11:02:37 2023 +0000

    block: remove the unused mode argument to ->release

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1340a3f0a80000
final oops:     https://syzkaller.appspot.com/x/report.txt?x=10c0a3f0a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1740a3f0a80000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+dfe2fbeb4e710bbaddf9@...kaller.appspotmail.com
Fixes: ae220766d87c ("block: remove the unused mode argument to ->release")

------------[ cut here ]------------
Unexpected user alpha2: �I
WARNING: CPU: 0 PID: 9 at net/wireless/reg.c:438 is_user_regdom_saved net/wireless/reg.c:438 [inline]
WARNING: CPU: 0 PID: 9 at net/wireless/reg.c:438 restore_alpha2 net/wireless/reg.c:3399 [inline]
WARNING: CPU: 0 PID: 9 at net/wireless/reg.c:438 restore_regulatory_settings+0x210/0x1760 net/wireless/reg.c:3491
Modules linked in:
CPU: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.4.0-next-20230630-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:438 [inline]
RIP: 0010:restore_alpha2 net/wireless/reg.c:3399 [inline]
RIP: 0010:restore_regulatory_settings+0x210/0x1760 net/wireless/reg.c:3491
Code: e6 03 44 89 f6 e8 50 d7 09 f8 45 84 f6 0f 85 7a 07 00 00 e8 62 db 09 f8 44 89 e2 44 89 ee 48 c7 c7 20 bc 9f 8b e8 c0 2b d1 f7 <0f> 0b e8 49 db 09 f8 48 8b 1d d2 80 f8 04 48 b8 00 00 00 00 00 fc
RSP: 0018:ffffc900000e7c30 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 00000000000000bf RCX: 0000000000000000
RDX: ffff888016a68000 RSI: ffffffff814c65a7 RDI: 0000000000000001
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000049
R13: 00000000000000bf R14: 0000000000000000 R15: ffff8880b983bb80
FS:  0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000140 CR3: 0000000073e5d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 crda_timeout_work+0x28/0x50 net/wireless/reg.c:540
 process_one_work+0xa34/0x16f0 kernel/workqueue.c:2597
 worker_thread+0x67d/0x10c0 kernel/workqueue.c:2748
 kthread+0x344/0x440 kernel/kthread.c:389
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </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 syzkaller@...glegroups.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

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

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.

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