syzbot


WARNING: locking bug in release_metapage (2)

Status: upstream: reported on 2025/04/10 17:25
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+07d59279835a55269ddf@syzkaller.appspotmail.com
First crash: 17d, last: 16h09m
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [jfs?] WARNING: locking bug in release_metapage (2) 0 (1) 2025/04/10 17:25
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING: locking bug in release_metapage jfs 3 182d 213d 0/28 auto-obsoleted due to no activity on 2025/01/31 10:54

Sample crash report:
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 0 PID: 6577 at kernel/locking/lockdep.c:237 hlock_class kernel/locking/lockdep.c:237 [inline]
WARNING: CPU: 0 PID: 6577 at kernel/locking/lockdep.c:237 check_wait_context kernel/locking/lockdep.c:4855 [inline]
WARNING: CPU: 0 PID: 6577 at kernel/locking/lockdep.c:237 __lock_acquire+0x356/0xd80 kernel/locking/lockdep.c:5185
Modules linked in:
CPU: 0 UID: 0 PID: 6577 Comm: syz.6.35 Not tainted 6.15.0-rc3-syzkaller-00019-gbc3372351d0c #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:hlock_class kernel/locking/lockdep.c:237 [inline]
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4855 [inline]
RIP: 0010:__lock_acquire+0x356/0xd80 kernel/locking/lockdep.c:5185
Code: 89 c3 90 e8 6c 45 5a 03 85 c0 74 22 83 3d 25 7d c0 0e 00 75 19 90 48 c7 c7 d6 0f 62 8e 48 c7 c6 3c 7e 54 8e e8 ab a7 e3 ff 90 <0f> 0b 90 90 90 31 c0 48 8b 74 24 08 41 89 d8 0f b6 98 c4 00 00 00
RSP: 0018:ffffc9000334f200 EFLAGS: 00010046
RAX: 95efbdef83889100 RBX: 0000000000000001 RCX: 0000000000080000
RDX: ffffc90004739000 RSI: 0000000000009860 RDI: 0000000000009861
RBP: ffff888026789e00 R08: ffffffff81821792 R09: 1ffffffff1d83338
R10: dffffc0000000000 R11: fffffbfff1d83339 R12: ffff88802678a9b0
R13: ffff888026789e00 R14: 0000000000000000 R15: ffff888078789330
FS:  00007f7b095556c0(0000) GS:ffff888124fcf000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4d8d664290 CR3: 0000000064bda000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0xd8/0x130 kernel/locking/spinlock.c:162
 __wake_up_common_lock+0x25/0x1e0 kernel/sched/wait.c:105
 unlock_metapage fs/jfs/jfs_metapage.c:39 [inline]
 release_metapage+0x158/0xa90 fs/jfs/jfs_metapage.c:763
 xtTruncate+0x1026/0x32a0 fs/jfs/jfs_xtree.c:-1
 jfs_truncate_nolock+0x364/0x420 fs/jfs/inode.c:373
 jfs_truncate fs/jfs/inode.c:412 [inline]
 jfs_write_failed+0x11a/0x190 fs/jfs/inode.c:289
 jfs_write_begin+0x64/0x70 fs/jfs/inode.c:301
 generic_perform_write+0x329/0xa10 mm/filemap.c:4103
 generic_file_write_iter+0x10e/0x5e0 mm/filemap.c:4246
 new_sync_write fs/read_write.c:591 [inline]
 vfs_write+0x70f/0xd10 fs/read_write.c:684
 ksys_write+0x19d/0x2d0 fs/read_write.c:736
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf3/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7b0878e169
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:00007f7b09555038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f7b089b5fa0 RCX: 00007f7b0878e169
RDX: 0000000000000020 RSI: 00002000000001c0 RDI: 0000000000000004
RBP: 00007f7b08810a68 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f7b089b5fa0 R15: 00007ffdeaa1b9e8
 </TASK>

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/23 15:00 upstream bc3372351d0c 53a8b9bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING: locking bug in release_metapage
2025/04/14 23:42 upstream 834a4a689699 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING: locking bug in release_metapage
2025/04/21 19:34 upstream 9d7a0577c9db 2a20f901 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING: locking bug in release_metapage
2025/04/09 00:47 upstream bec7dcbc242c b133e63a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING: locking bug in release_metapage
2025/04/06 17:19 upstream f4d2ef48250a 1c65791e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING: locking bug in release_metapage
* Struck through repros no longer work on HEAD.