[v6.1] WARNING in kthread_bind_mask

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ca87e77a2ef8 Linux 6.1.34
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15c2f6bb280000
kernel config: https://syzkaller.appspot.com/x/.config?x=c188e92022a334b
dashboard link: https://syzkaller.appspot.com/bug?extid=66cf6e29eb3ba11a0f22
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=12bd33c3280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f48d514c343c/disk-ca87e77a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/563336f1f216/vmlinux-ca87e77a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2254afa3642b/bzImage-ca87e77a.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 3865 at kernel/kthread.c:524 kthread_bind_mask+0x90/0xc0 kernel/kthread.c:542
Modules linked in:
CPU: 1 PID: 3865 Comm: syz-executor.3 Not tainted 6.1.34-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:__kthread_bind_mask kernel/kthread.c:524 [inline]
RIP: 0010:kthread_bind_mask+0x90/0xc0 kernel/kthread.c:542
Code: 00 fc ff df 0f b6 04 08 84 c0 75 2a 41 80 4d 03 04 4c 89 f7 4c 89 e6 5b 41 5c 41 5d 41 5e 41 5f e9 35 b1 31 09 e8 30 65 2e 00 <0f> 0b 5b 41 5c 41 5d 41 5e 41 5f c3 44 89 e9 80 e1 07 80 c1 03 38
RSP: 0018:ffffc90004d9fb58 EFLAGS: 00010293
RAX: ffffffff815b7020 RBX: 0000000000000000 RCX: ffff888021d5bb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 1ffff110045b0828 R08: ffffffff815b6fbe R09: ffffed100462b141
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888022d84140
R13: ffff888023158000 R14: ffff888063a718f8 R15: ffffffff8e5326b8
FS: 0000555557482400(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200018c5 CR3: 000000006477b000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
init_rescuer+0x225/0x290 kernel/workqueue.c:4282
alloc_workqueue+0xf3d/0x1440 kernel/workqueue.c:4349
kvm_mmu_init_tdp_mmu+0x79/0x1e0 arch/x86/kvm/mmu/tdp_mmu.c:24
kvm_mmu_init_vm+0x10e/0x2a0 arch/x86/kvm/mmu/mmu.c:6002
kvm_arch_init_vm+0x52/0x620 arch/x86/kvm/x86.c:12432
kvm_create_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:1201 [inline]
kvm_dev_ioctl_create_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:4967 [inline]
kvm_dev_ioctl+0xb24/0x1860 arch/x86/kvm/../../../virt/kvm/kvm_main.c:5009
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f689e88c389
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd6e2fc318 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f689e9abf80 RCX: 00007f689e88c389
RDX: 0000000000000000 RSI: 000000000000ae01 RDI: 0000000000000003
RBP: 00007f689e8d7493 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f689e400448 R14: 00007f689e9abf80 R15: 0000000000000000
</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 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