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

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: <67cd6b29.050a0220.24a339.00c9.GAE@google.com>
Date: Sun, 09 Mar 2025 03:19:21 -0700
From: syzbot <syzbot+21e941390e11695ad9e1@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [kernel?] WARNING: locking bug in alloc_pid

Hello,

syzbot found the following issue on:

HEAD commit:    e056da87c780 Merge remote-tracking branch 'will/for-next/p..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1103d7a0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d6b7e15dc5b5e776
dashboard link: https://syzkaller.appspot.com/bug?extid=21e941390e11695ad9e1
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3d8b1b7cc4c0/disk-e056da87.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b84c04cff235/vmlinux-e056da87.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2ae4d0525881/Image-e056da87.gz.xz

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

------------[ cut here ]------------
Looking for class "->lock" with key init_kmem_cache_cpus.__key, but found a different class "&c->lock" with the same key
WARNING: CPU: 1 PID: 7232 at kernel/locking/lockdep.c:941 look_up_lock_class+0xec/0x160 kernel/locking/lockdep.c:938
Modules linked in:
CPU: 1 UID: 0 PID: 7232 Comm: syz.1.161 Not tainted 6.14.0-rc4-syzkaller-ge056da87c780 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : look_up_lock_class+0xec/0x160 kernel/locking/lockdep.c:938
lr : look_up_lock_class+0xec/0x160 kernel/locking/lockdep.c:938
sp : ffff80009edc7120
x29: ffff80009edc7120 x28: dfff800000000000 x27: 0000000000000000
x26: ffff800097797900 x25: ffff800097797000 x24: 0000000000000001
x23: 0000000000000000 x22: 1ffff00011f780cb x21: ffff8000977f86e0
x20: fffffdffbf7049e0 x19: ffff80009326a528 x18: 0000000000000008
x17: 202c79656b5f5f2e x16: ffff8000832b5180 x15: 0000000000000001
x14: 1fffe000366f60f2 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000080000 x10: 000000000007e053 x9 : 97b380b684c48600
x8 : 97b380b684c48600 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80009edc68d8 x4 : ffff80008fcaf780 x3 : ffff800080741744
x2 : 0000000000000001 x1 : 0000000100000001 x0 : 0000000000000000
Call trace:
 look_up_lock_class+0xec/0x160 kernel/locking/lockdep.c:938 (P)
 register_lock_class+0x8c/0x6b4 kernel/locking/lockdep.c:1292
 __lock_acquire+0x18c/0x7904 kernel/locking/lockdep.c:5103
 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851
 local_lock_acquire+0x3c/0x98 include/linux/local_lock_internal.h:29
 ___slab_alloc+0xcd0/0xf4c mm/slub.c:3875
 __slab_alloc+0x74/0xd0 mm/slub.c:3916
 __slab_alloc_node mm/slub.c:3991 [inline]
 slab_alloc_node mm/slub.c:4152 [inline]
 kmem_cache_alloc_noprof+0x300/0x410 mm/slub.c:4171
 alloc_pid+0xac/0xba8 kernel/pid.c:184
 copy_process+0x1a4c/0x322c kernel/fork.c:2419
 kernel_clone+0x1d8/0x82c kernel/fork.c:2815
 __do_sys_clone kernel/fork.c:2958 [inline]
 __se_sys_clone kernel/fork.c:2926 [inline]
 __arm64_sys_clone+0x1f8/0x270 kernel/fork.c:2926
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0x1e0/0x23c arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744
 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600
irq event stamp: 1218
hardirqs last  enabled at (1217): [<ffff80008b7e75f8>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last  enabled at (1217): [<ffff80008b7e75f8>] _raw_spin_unlock_irqrestore+0x38/0x98 kernel/locking/spinlock.c:194
hardirqs last disabled at (1218): [<ffff800080b57dc8>] ___slab_alloc+0xca4/0xf4c mm/slub.c:3875
softirqs last  enabled at (800): [<ffff800080311b48>] softirq_handle_end kernel/softirq.c:407 [inline]
softirqs last  enabled at (800): [<ffff800080311b48>] handle_softirqs+0xb44/0xd34 kernel/softirq.c:589
softirqs last disabled at (777): [<ffff800080020dbc>] __do_softirq+0x14/0x20 kernel/softirq.c:595
---[ end trace 0000000000000000 ]---


---
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