linux-kernel - [syzbot] [kernel?] WARNING: locking bug in process_one

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: <6712654e.050a0220.10f4f4.0014.GAE@google.com>
Date: Fri, 18 Oct 2024 06:40:30 -0700
From: syzbot <syzbot+b1e6570b82775975e1bb@...kaller.appspotmail.com>
To: bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com, 
	linux-kernel@...r.kernel.org, mingo@...hat.com, 
	syzkaller-bugs@...glegroups.com, tglx@...utronix.de, x86@...nel.org
Subject: [syzbot] [kernel?] WARNING: locking bug in process_one_work (6)

Hello,

syzbot found the following issue on:

HEAD commit:    6485cf5ea253 Merge tag 'hid-for-linus-2024101301' of git:/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12ea385f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4c9b3fd66df7ebb7
dashboard link: https://syzkaller.appspot.com/bug?extid=b1e6570b82775975e1bb
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-6485cf5e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fcb92964a345/vmlinux-6485cf5e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4f66a07fe646/bzImage-6485cf5e.xz

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

WARNING: CPU: 0 PID: 1419 at kernel/locking/lockdep.c:936 look_up_lock_class+0x140/0x150 kernel/locking/lockdep.c:936
Modules linked in:
CPU: 0 UID: 0 PID: 1419 Comm: kworker/0:3 Not tainted 6.12.0-rc3-syzkaller-00007-g6485cf5ea253 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: wg-kex-wg1 wg_packet_handshake_receive_worker
RIP: 0010:look_up_lock_class+0x140/0x150 kernel/locking/lockdep.c:936
Code: c7 c7 60 cf 6c 8b e8 2f 8f 2c f6 90 0f 0b 90 90 90 31 db eb be c6 05 c5 14 26 05 01 90 48 c7 c7 40 d2 6c 8b e8 11 8f 2c f6 90 <0f> 0b 90 90 e9 58 ff ff ff 0f 1f 80 00 00 00 00 90 90 90 90 90 90
RSP: 0018:ffffc90006baf988 EFLAGS: 00010086
RAX: 0000000000000000 RBX: ffffffff96e97090 RCX: ffffffff814e71a9
RDX: ffff888027dc8000 RSI: ffffffff814e71b6 RDI: 0000000000000001
RBP: ffffffff9ab0ac60 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 20676e696b6f6f4c R12: ffffc90006bafd80
R13: 0000000000000000 R14: 0000000000000000 R15: ffffffff9a821820
FS:  0000000000000000(0000) GS:ffff88806a600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200f7000 CR3: 000000005e206000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 register_lock_class+0xb1/0x1240 kernel/locking/lockdep.c:1290
 __lock_acquire+0x135/0x3ce0 kernel/locking/lockdep.c:5077
 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5825
 process_one_work+0x927/0x1ba0 kernel/workqueue.c:3205
 process_scheduled_works kernel/workqueue.c:3310 [inline]
 worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391
 kthread+0x2c1/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x45/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