Subject: [syzbot] [kernel?] linux-next test error: WARNING in alloc_workqueue

From: syzbot <[email-masked]>
Date: Fri, 19 Jul 2024 01:09:24 -0700

Hello,

syzbot found the following issue on:

HEAD commit:    91e3b24eb7d2 Add linux-next specific files for 20240715
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1700fb31980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7b6bd2d463871440
dashboard link: https://syzkaller.appspot.com/bug?extid=0140d5dae274b92d2400
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b844ec41aa74/disk-91e3b24e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/391d0a06ddd9/vmlinux-91e3b24e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/71388f4b21d9/bzImage-91e3b24e.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email-masked]

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5097 at kernel/cpu.c:527 lockdep_assert_cpus_held+0xad/0x100 kernel/cpu.c:527
Modules linked in:
CPU: 1 UID: 0 PID: 5097 Comm: syz-executor Not tainted 6.10.0-next-20240715-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:lockdep_assert_cpus_held+0xad/0x100 kernel/cpu.c:527
Code: 0a 89 c3 31 ff 89 c6 e8 81 17 3e 00 85 db 74 14 e8 38 13 3e 00 eb 05 e8 31 13 3e 00 5b 41 5e c3 cc cc cc cc e8 24 13 3e 00 90 <0f> 0b 90 eb ed 48 c7 c1 40 ad af 8f 80 e1 07 80 c1 03 38 c1 0f 8c
RSP: 0018:ffffc9000354f8a8 EFLAGS: 00010293
RAX: ffffffff8155b7cc RBX: 0000000000000000 RCX: ffff888028341e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000354fa80 R08: ffffffff8155b7af R09: 1ffffffff1f6000d
R10: dffffc0000000000 R11: fffffbfff1f6000e R12: dffffc0000000000
R13: ffff88801fc28800 R14: dffffc0000000000 R15: ffff8881426f9880
FS:  0000555557025500(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000564978912b08 CR3: 0000000021990000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 alloc_and_link_pwqs kernel/workqueue.c:5437 [inline]
 alloc_workqueue+0xbc8/0x1fe0 kernel/workqueue.c:5703
 tipc_crypto_start+0xd2/0x620 net/tipc/crypto.c:1472
 tipc_init_net+0x211/0x330 net/tipc/core.c:72
 ops_init+0x359/0x610 net/core/net_namespace.c:139
 setup_net+0x515/0xca0 net/core/net_namespace.c:343
 copy_net_ns+0x4e2/0x7b0 net/core/net_namespace.c:508
 create_new_namespaces+0x425/0x7b0 kernel/nsproxy.c:110
 unshare_nsproxy_namespaces+0x124/0x180 kernel/nsproxy.c:228
 ksys_unshare+0x619/0xc10 kernel/fork.c:3316
 __do_sys_unshare kernel/fork.c:3387 [inline]
 __se_sys_unshare kernel/fork.c:3385 [inline]
 __x64_sys_unshare+0x38/0x40 kernel/fork.c:3385
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4a15177337
Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 10 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff67fdb2c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000110
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f4a15177337
RDX: 00007f4a15175bd9 RSI: 00007fff67fdb290 RDI: 0000000040000000
RBP: 00007fff67fdb2f8 R08: 00007f4a152c3a30 R09: 00007f4a152c3a30
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff67fdb2f0
R13: 00007fff67fdb578 R14: 0000000000000009 R15: 0000000000000009
 </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 [email-masked].

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