linux-kernel - [syzbot] [mm?] bpf 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>] [day] [month] [year] [list]

Message-ID: <6780eb0a.050a0220.d0267.0027.GAE@google.com>
Date: Fri, 10 Jan 2025 01:40:26 -0800
From: syzbot <syzbot+88988cfce8f3aa42cc80@...kaller.appspotmail.com>
To: akpm@...ux-foundation.org, ast@...nel.org, daniel@...earbox.net, 
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, netdev@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [mm?] bpf test error: WARNING in enable_work

Hello,

syzbot found the following issue on:

HEAD commit:    9d89551994a4 Linux 6.13-rc6
git tree:       bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=122ac1df980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4ef22c4fce5135b4
dashboard link: https://syzkaller.appspot.com/bug?extid=88988cfce8f3aa42cc80
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/9bc45dda6651/disk-9d895519.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/34e0e0deceda/vmlinux-9d895519.xz
kernel image: https://storage.googleapis.com/syzbot-assets/503e9fd75086/bzImage-9d895519.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+88988cfce8f3aa42cc80@...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+0x34d/0x360 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+0x34d/0x360 kernel/workqueue.c:4488
Code: d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 18 82 37 00 c6 05 f9 ac 9b 0e 01 90 48 c7 c7 00 d7 09 8c e8 d4 25 f8 ff 90 <0f> 0b 90 90 e9 56 ff ff ff e8 b5 c7 60 0a 0f 1f 44 00 00 90 90 90
RSP: 0000:ffffc900001c7bc0 EFLAGS: 00010046
RAX: 7f171ad72ec7e200 RBX: 0000000000000000 RCX: ffff88801d2f3c00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900001c7c88 R08: ffffffff81602a82 R09: 1ffffffff1cfa210
R10: dffffc0000000000 R11: fffffbfff1cfa211 R12: 1ffff92000038f7c
R13: 1ffff92000038f84 R14: 001fffffffc00001 R15: ffff8880b8738770
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:1102
 smpboot_thread_fn+0x544/0xa30 kernel/smpboot.c:164
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/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