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: <0000000000006a5beb06190ba6d2@google.com>
Date: Wed, 22 May 2024 07:21:27 -0700
From: syzbot <syzbot+2dd3f44b0f42f3aee4ec@...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 (5)

Hello,

syzbot found the following issue on:

HEAD commit:    4b377b4868ef kprobe/ftrace: fix build error due to bad fun..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17096d92980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=11eee78d9c5171fd
dashboard link: https://syzkaller.appspot.com/bug?extid=2dd3f44b0f42f3aee4ec
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-4b377b48.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b158356f72a3/vmlinux-4b377b48.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3bdecd8d3c89/bzImage-4b377b48.xz

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

------------[ cut here ]------------
Looking for class "ork_completion)(&sdp->work)" with key __key.5, but found a different class "(work_completion)(&sdp->work)" with the same key
WARNING: CPU: 0 PID: 8 at kernel/locking/lockdep.c:932 look_up_lock_class+0x133/0x140 kernel/locking/lockdep.c:932
Modules linked in:
CPU: 0 PID: 8 Comm: kworker/0:0 Not tainted 6.9.0-syzkaller-08544-g4b377b4868ef #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: rcu_gp srcu_invoke_callbacks
RIP: 0010:look_up_lock_class+0x133/0x140 kernel/locking/lockdep.c:932
Code: c7 c7 e0 b3 2c 8b e8 3c 25 74 f6 90 0f 0b 90 90 90 31 db eb be c6 05 8e aa ee 04 01 90 48 c7 c7 00 b7 2c 8b e8 1e 25 74 f6 90 <0f> 0b 90 90 e9 62 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc900003a7988 EFLAGS: 00010086
RAX: 0000000000000000 RBX: ffffffff941f8e58 RCX: ffffffff81510469
RDX: ffff888015f22440 RSI: ffffffff81510476 RDI: 0000000000000001
RBP: ffffffff94ac4880 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 20676e696b6f6f4c R12: ffffc900003a7d80
R13: 0000000000000000 R14: 0000000000000000 R15: ffffffff94ac3ba0
FS:  0000000000000000(0000) GS:ffff88802c000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000f743a0c4 CR3: 000000002a136000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 register_lock_class+0xb1/0x1230 kernel/locking/lockdep.c:1284
 __lock_acquire+0x111/0x3b30 kernel/locking/lockdep.c:5014
 lock_acquire kernel/locking/lockdep.c:5754 [inline]
 lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5719
 process_one_work+0x8c4/0x1ad0 kernel/workqueue.c:3207
 process_scheduled_works kernel/workqueue.c:3312 [inline]
 worker_thread+0x6c8/0xf70 kernel/workqueue.c:3393
 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