linux-kernel - [syzbot] [mm?] upstream test error: WARNING in enable

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: <678033fe.050a0220.25a300.01ce.GAE@google.com>
Date: Thu, 09 Jan 2025 12:39:26 -0800
From: syzbot <syzbot+0bef82da8b7dca7e5869@...kaller.appspotmail.com>
To: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, 
	linux-mm@...ck.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [mm?] upstream test error: WARNING in enable_work

Hello,

syzbot found the following issue on:

HEAD commit:    9d89551994a4 Linux 6.13-rc6
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1180b9c4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=10cb4f23d3e0f104
dashboard link: https://syzkaller.appspot.com/bug?extid=0bef82da8b7dca7e5869
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ac26b8628463/disk-9d895519.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/05387975b936/vmlinux-9d895519.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c28b69047c4b/bzImage-9d895519.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0bef82da8b7dca7e5869@...kaller.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+0x2fa/0x340 kernel/workqueue.c:4488
Modules linked in:
CPU: 1 UID: 0 PID: 22 Comm: cpuhp/1 Not tainted 6.13.0-rc6-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+0x2fa/0x340 kernel/workqueue.c:4488
Code: 89 ee e8 b9 d5 36 00 45 84 ed 0f 85 28 fe ff ff e8 0b db 36 00 c6 05 90 c1 e4 0e 01 90 48 c7 c7 e0 d9 6b 8b e8 57 12 f7 ff 90 <0f> 0b 90 90 e9 05 fe ff ff 48 89 ef e8 e5 a5 98 00 e9 a9 fe ff ff
RSP: 0018:ffffc900001c7ca0 EFLAGS: 00010082
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff815a5139
RDX: ffff88801d69bc00 RSI: ffffffff815a5146 RDI: 0000000000000001
RBP: ffff8880b8738660 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000002 R12: 1ffff92000038f95
R13: 0000000000000000 R14: 00000000000000c4 R15: ffffffff81db2390
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000df7e000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 vmstat_cpu_online+0x83/0xf0 mm/vmstat.c:2151
 cpuhp_invoke_callback+0x3d3/0xa10 kernel/cpu.c:194
 cpuhp_thread_fun+0x480/0x6f0 kernel/cpu.c:1102
 smpboot_thread_fn+0x664/0xa30 kernel/smpboot.c:164
 kthread+0x2c4/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147
 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@...glegroups.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