syzbot


possible deadlock in jbd2_log_wait_commit

Status: upstream: reported on 2024/12/08 12:28
Reported-by: syzbot+baaa0f0c7207b20b883b@syzkaller.appspotmail.com
First crash: 221d, last: 23d
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in jbd2_log_wait_commit ext4 4 C done 429 846d 870d 22/29 fixed on 2023/06/08 14:41

Sample crash report:
(syz-executor,6522,0):ocfs2_replay_truncate_records:5975 ERROR: status = -30
(syz-executor,6522,0):__ocfs2_flush_truncate_log:6056 ERROR: status = -30
(syz-executor,6522,0):ocfs2_sync_fs:405 ERROR: status = -30
============================================
WARNING: possible recursive locking detected
5.15.185-syzkaller #0 Not tainted
--------------------------------------------
syz-executor/6522 is trying to acquire lock:
ffff88801fab2990 (jbd2_handle){++++}-{0:0}, at: jbd2_log_wait_commit+0x14e/0x4a0 fs/jbd2/journal.c:697

but task is already holding lock:
ffff88801fab2990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x1312/0x15a0 fs/jbd2/transaction.c:462

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(jbd2_handle);
  lock(jbd2_handle);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

4 locks held by syz-executor/6522:
 #0: ffff88807e1060e0 (&type->s_umount_key#79){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:365
 #1: ffff88807e106650 (sb_internal#5){.+.+}-{0:0}, at: ocfs2_replay_truncate_records fs/ocfs2/alloc.c:5939 [inline]
 #1: ffff88807e106650 (sb_internal#5){.+.+}-{0:0}, at: __ocfs2_flush_truncate_log+0x46a/0x1060 fs/ocfs2/alloc.c:6053
 #2: ffff88804ac048e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x368/0x6c0 fs/ocfs2/journal.c:374
 #3: ffff88801fab2990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x1312/0x15a0 fs/jbd2/transaction.c:462

stack backtrace:
CPU: 0 PID: 6522 Comm: syz-executor Not tainted 5.15.185-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 __lock_acquire+0x1227/0x7c60 kernel/locking/lockdep.c:-1
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 jbd2_log_wait_commit+0x16a/0x4a0 fs/jbd2/journal.c:697
 ocfs2_sync_fs+0x217/0x310 fs/ocfs2/super.c:413
 sync_filesystem+0x1be/0x220 fs/sync.c:66
 generic_shutdown_super+0x6b/0x300 fs/super.c:448
 kill_block_super+0x7c/0xe0 fs/super.c:1427
 deactivate_locked_super+0x93/0xf0 fs/super.c:335
 cleanup_mnt+0x418/0x4d0 fs/namespace.c:1139
 task_work_run+0x125/0x1a0 kernel/task_work.c:188
 tracehook_notify_resume include/linux/tracehook.h:189 [inline]
 exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181
 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214
 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
 syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f736bb4fc57
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffd92874968 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f736bbd0925 RCX: 00007f736bb4fc57
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffd92874a20
RBP: 00007ffd92874a20 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffd92875ab0
R13: 00007f736bbd0925 R14: 0000000000047a8d R15: 00007ffd92875af0
 </TASK>

Crashes (29):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/24 03:37 linux-5.15.y 1c700860e8bc e2f27c35 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2025/06/23 03:27 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2025/06/22 18:32 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2025/06/21 18:07 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2025/06/21 18:06 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2025/06/21 18:05 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2025/06/21 18:04 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2025/06/21 18:04 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2025/03/08 03:58 linux-5.15.y c16c81c81336 7e3bd60d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2025/03/08 03:58 linux-5.15.y c16c81c81336 7e3bd60d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2024/12/08 12:30 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2024/12/08 12:27 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2024/12/08 12:27 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in jbd2_log_wait_commit
2025/06/21 15:35 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/06/21 15:34 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/06/21 15:32 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/06/21 15:30 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/06/21 15:28 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/06/21 15:20 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/05/31 02:38 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/05/31 02:38 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/03/20 08:39 linux-5.15.y 0c935c049b5c 9209bc22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/03/20 08:36 linux-5.15.y 0c935c049b5c 9209bc22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/03/20 08:36 linux-5.15.y 0c935c049b5c 9209bc22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/03/19 19:33 linux-5.15.y 0c935c049b5c e20d7b13 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/03/19 19:33 linux-5.15.y 0c935c049b5c e20d7b13 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/03/19 09:52 linux-5.15.y 0c935c049b5c 8d0a2921 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/03/19 09:50 linux-5.15.y 0c935c049b5c 8d0a2921 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
2025/03/19 09:50 linux-5.15.y 0c935c049b5c 8d0a2921 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in jbd2_log_wait_commit
* Struck through repros no longer work on HEAD.