syzbot


WARNING: locking bug in jbd2_alloc

Status: upstream: reported on 2024/11/28 05:37
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+92b9109f47b38b1a6657@syzkaller.appspotmail.com
First crash: 124d, last: 2d12h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ext4?] WARNING: locking bug in jbd2_alloc 0 (1) 2024/11/28 05:37

Sample crash report:
ocfs2: Slot 0 on device (7,1) was already allocated to this node!
ocfs2: Mounting device (7,1) on (node local, slot 0) with ordered data mode.
------------[ 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: 6891 at kernel/locking/lockdep.c:944 look_up_lock_class+0xe0/0x170 kernel/locking/lockdep.c:941
Modules linked in:
CPU: 1 UID: 0 PID: 6891 Comm: syz.1.187 Not tainted 6.14.0-syzkaller-01103-g2df0c02dab82 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:look_up_lock_class+0xe0/0x170 kernel/locking/lockdep.c:941
Code: 01 0f 85 8a 00 00 00 c6 05 16 34 13 04 01 90 49 8b 16 49 8b 76 18 48 8b 8b b8 00 00 00 48 c7 c7 1d c5 2a 8e e8 61 b4 6f f5 90 <0f> 0b 90 90 eb 61 90 e8 d4 f4 dd f8 e8 5f 31 90 f5 48 c7 c7 c3 c4
RSP: 0018:ffffc900033664a8 EFLAGS: 00010046
RAX: b770cafbb29a0700 RBX: ffffffff93e530e0 RCX: 0000000000080000
RDX: ffffc90005103000 RSI: 0000000000006aa0 RDI: 0000000000006aa1
RBP: ffff8880302d0000 R08: ffffffff81826ce2 R09: 1ffff110170e47d2
R10: dffffc0000000000 R11: ffffed10170e47d3 R12: ffffffff9a4d5780
R13: ffffffff933c6020 R14: ffffe8ffffd6fa30 R15: ffffffff933c6020
FS:  00007f43f0f2e6c0(0000) GS:ffff88812535a000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2fb15ff8 CR3: 00000000306e8000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 register_lock_class+0x54/0x330 kernel/locking/lockdep.c:1295
 __lock_acquire+0x80/0xd80 kernel/locking/lockdep.c:5110
 lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866
 local_lock_acquire+0x20/0x80 include/linux/local_lock_internal.h:29
 ___slab_alloc+0x11e1/0x1500 mm/slub.c:3898
 __slab_alloc+0x58/0xa0 mm/slub.c:3939
 __slab_alloc_node mm/slub.c:4014 [inline]
 slab_alloc_node mm/slub.c:4175 [inline]
 kmem_cache_alloc_noprof+0x270/0x390 mm/slub.c:4194
 jbd2_alloc+0x155/0x1b0 fs/jbd2/journal.c:2763
 jbd2_journal_get_undo_access+0x1d1/0x310 fs/jbd2/transaction.c:1395
 __ocfs2_journal_access+0x4eb/0x8e0 fs/ocfs2/journal.c:692
 ocfs2_block_group_set_bits+0x2a0/0x9d0 fs/ocfs2/suballoc.c:1387
 ocfs2_search_chain+0x1bbf/0x2770 fs/ocfs2/suballoc.c:1900
 ocfs2_claim_suballoc_bits+0x11fc/0x2570 fs/ocfs2/suballoc.c:1985
 __ocfs2_claim_clusters+0x343/0xa50 fs/ocfs2/suballoc.c:2395
 ocfs2_claim_clusters fs/ocfs2/suballoc.c:2432 [inline]
 ocfs2_block_group_alloc_contig fs/ocfs2/suballoc.c:432 [inline]
 ocfs2_block_group_alloc fs/ocfs2/suballoc.c:699 [inline]
 ocfs2_reserve_suballoc_bits+0x1216/0x4f30 fs/ocfs2/suballoc.c:832
 ocfs2_reserve_new_metadata_blocks+0x41c/0x9b0 fs/ocfs2/suballoc.c:982
 ocfs2_mknod+0x143e/0x2b30 fs/ocfs2/namei.c:347
 vfs_mknod+0x36d/0x3b0 fs/namei.c:4193
 do_mknodat+0x473/0x600
 __do_sys_mknodat fs/namei.c:4271 [inline]
 __se_sys_mknodat fs/namei.c:4268 [inline]
 __x64_sys_mknodat+0xa7/0xc0 fs/namei.c:4268
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f43f018d169
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f43f0f2e038 EFLAGS: 00000246 ORIG_RAX: 0000000000000103
RAX: ffffffffffffffda RBX: 00007f43f03a5fa0 RCX: 00007f43f018d169
RDX: 0000000000006000 RSI: 0000200000000000 RDI: ffffffffffffff9c
RBP: 00007f43f020e2a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000703 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f43f03a5fa0 R15: 00007ffe3d9df7b8
 </TASK>

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/25 18:19 upstream 2df0c02dab82 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING: locking bug in jbd2_alloc
2025/03/07 08:12 upstream 0f52fd4f67c6 831e3629 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING: locking bug in jbd2_alloc
2025/01/20 11:14 upstream ffd294d346d1 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING: locking bug in jbd2_alloc
2024/12/31 07:57 upstream ccb98ccef0e5 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING: locking bug in jbd2_alloc
2024/12/26 10:20 upstream 9b2ffa6148b1 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING: locking bug in jbd2_alloc
2024/12/14 21:40 upstream a446e965a188 7cbfbb3a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING: locking bug in jbd2_alloc
2024/11/24 05:35 upstream 9f16d5e6f220 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING: locking bug in jbd2_alloc
* Struck through repros no longer work on HEAD.