[syzbot] [mm?] linux-next test error: WARNING in enable_work

[syzbot <syzbot+722a07ef96b37455090d@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    4e16367cfe0c Add linux-next specific files for 20250106
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=143344b0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ab790aab796d34a9
dashboard link: https://syzkaller.appspot.com/bug?extid=722a07ef96b37455090d
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/403cb64e30da/disk-4e16367c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ccd3dbdc32f4/vmlinux-4e16367c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/32256ded47b5/bzImage-4e16367c.xz

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

------------[ cut here ]------------
workqueue: work disable count underflowed
WARNING: CPU: 1 PID: 22 at kernel/workqueue.c:4317 work_offqd_enable kernel/workqueue.c:4317 [inline]
WARNING: CPU: 1 PID: 22 at kernel/workqueue.c:4317 enable_work+0x34d/0x360 kernel/workqueue.c:4488
Modules linked in:
CPU: 1 UID: 0 PID: 22 Comm: cpuhp/1 Not tainted 6.13.0-rc5-next-20250106-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:work_offqd_enable kernel/workqueue.c:4317 [inline]
RIP: 0010:enable_work+0x34d/0x360 kernel/workqueue.c:4488
Code: d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 08 69 37 00 c6 05 e3 0b 7d 0e 01 90 48 c7 c7 80 d7 09 8c e8 74 23 f8 ff 90 <0f> 0b 90 90 e9 56 ff ff ff e8 a5 6a 6a 0a 0f 1f 44 00 00 90 90 90
RSP: 0000:ffffc900001c7b20 EFLAGS: 00010046
RAX: c75b2868096bc700 RBX: 0000000000000000 RCX: ffff88801d683c00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900001c7be8 R08: ffffffff817ff732 R09: 1ffffffff1cfa188
R10: dffffc0000000000 R11: fffffbfff1cfa189 R12: 1ffff92000038f68
R13: 1ffff92000038f70 R14: 001fffffffc00001 R15: ffff8880b87383f0
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000e736000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 vmstat_cpu_online+0xbb/0xe0 mm/vmstat.c:2151
 cpuhp_invoke_callback+0x48d/0x830 kernel/cpu.c:194
 cpuhp_thread_fun+0x41c/0x810 kernel/cpu.c:1103
 smpboot_thread_fn+0x544/0xa30 kernel/smpboot.c:164
 kthread+0x7a9/0x920 kernel/kthread.c:464
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </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@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