possible deadlock in jbd2_log_wait_commit (2)

Status: upstream: reported on 2026/11/18 19:36
Reported-by: syzbot+6edbe585ab77fe9aa4a5@syzkaller.appspotmail.com
First crash: 18h52m, last: 18h52m
▶ ▼ Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in jbd2_log_wait_commit 4 29 513d 711d 0/3 auto-obsoleted due to no activity on 2025/09/29 15:37
linux-5.15 possible deadlock in jbd2_log_wait_commit (2) origin:lts-only 4 syz, C error 963 3h44m 333d 0/3 upstream: reported C repro on 2025/12/20 23:03
linux-6.1 possible deadlock in jbd2_log_wait_commit 4 2 230d 247d 0/3 auto-obsoleted due to no activity on 2026/07/12 02:17
upstream possible deadlock in jbd2_log_wait_commit ext4 4 syz, C done 429 1335d 1359d 22/29 fixed on 2023/06/08 14:41

Sample crash report:
JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,3) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.3.758/6497 is trying to acquire lock:
ffff0000d7296990 (jbd2_handle){++++}-{0:0}, at: jbd2_log_wait_commit+0x128/0x438 fs/jbd2/journal.c:693

but task is already holding lock:
ffff0000e23b94a0 (&ocfs2_quota_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_write_begin+0x190/0x318 fs/ocfs2/aops.c:1904

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&ocfs2_quota_ip_alloc_sem_key){++++}-{3:3}:
       down_write+0x5c/0x88 kernel/locking/rwsem.c:1573
       ocfs2_create_local_dquot+0x140/0x1444 fs/ocfs2/quota_local.c:1224
       ocfs2_acquire_dquot+0x6dc/0xab0 fs/ocfs2/quota_global.c:871
       dqget+0x638/0xa98 fs/quota/dquot.c:1013
       dquot_get_next_dqblk+0xb4/0x340 fs/quota/dquot.c:2745
       quota_getnextquota+0x258/0x494 fs/quota/quota.c:250
       do_quotactl+0x41c/0x738 fs/quota/quota.c:800
       __do_sys_quotactl fs/quota/quota.c:960 [inline]
       __se_sys_quotactl fs/quota/quota.c:916 [inline]
       __arm64_sys_quotactl+0x2dc/0x77c fs/quota/quota.c:916
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x12c arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:589

-> #2 (&dquot->dq_lock){+.+.}-{3:3}:
       __mutex_lock_common+0x1a0/0x1f88 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
       dquot_commit+0x54/0x1c8 fs/quota/dquot.c:535
       ext4_write_dquot+0x1b4/0x320 fs/ext4/super.c:6824
       ext4_mark_dquot_dirty+0xe8/0x150 fs/ext4/super.c:6901
       mark_dquot_dirty fs/quota/dquot.c:400 [inline]
       mark_all_dquot_dirty+0x108/0x424 fs/quota/dquot.c:440
       __dquot_alloc_space+0x564/0xcfc fs/quota/dquot.c:1777
       dquot_alloc_space_nodirty include/linux/quotaops.h:293 [inline]
       dquot_alloc_space include/linux/quotaops.h:306 [inline]
       dquot_alloc_block include/linux/quotaops.h:330 [inline]
       ext4_mb_new_blocks+0xd40/0x4244 fs/ext4/mballoc.c:5755
       ext4_alloc_branch fs/ext4/indirect.c:340 [inline]
       ext4_ind_map_blocks+0xcc0/0x1d78 fs/ext4/indirect.c:635
       ext4_map_blocks+0x768/0x160c fs/ext4/inode.c:683
       ext4_getblk+0x178/0x680 fs/ext4/inode.c:892
       ext4_bread+0x3c/0x1a8 fs/ext4/inode.c:948
       ext4_append+0x23c/0x488 fs/ext4/namei.c:83
       ext4_init_new_dir+0x270/0x4f0 fs/ext4/namei.c:3032
       ext4_mkdir+0x3b8/0xa28 fs/ext4/namei.c:3078
       vfs_mkdir+0x314/0x4d8 fs/namei.c:4161
       do_mkdirat+0x1b8/0x3ec fs/namei.c:4186
       __do_sys_mkdirat fs/namei.c:4201 [inline]
       __se_sys_mkdirat fs/namei.c:4199 [inline]
       __arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4199
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x12c arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:589

-> #1 (&ei->i_data_sem){++++}-{3:3}:
       down_write+0x5c/0x88 kernel/locking/rwsem.c:1573
       ext4_map_blocks+0x720/0x160c fs/ext4/inode.c:674
       mpage_map_one_extent fs/ext4/inode.c:2437 [inline]
       mpage_map_and_submit_extent fs/ext4/inode.c:2490 [inline]
       ext4_writepages+0x10a4/0x29f0 fs/ext4/inode.c:2859
       do_writepages+0x2c4/0x50c mm/page-writeback.c:2491
       __writeback_single_inode+0x164/0x157c fs/fs-writeback.c:1688
       writeback_sb_inodes+0x870/0x1470 fs/fs-writeback.c:1979
       __writeback_inodes_wb+0x104/0x370 fs/fs-writeback.c:2050
       wb_writeback+0x420/0xfdc fs/fs-writeback.c:2155
       wb_check_background_flush fs/fs-writeback.c:2221 [inline]
       wb_do_writeback fs/fs-writeback.c:2309 [inline]
       wb_workfn+0xb40/0xe18 fs/fs-writeback.c:2336
       process_one_work+0x7e4/0x13bc kernel/workqueue.c:2292
       worker_thread+0x8cc/0xfe8 kernel/workqueue.c:2439
       kthread+0x254/0x2e0 kernel/kthread.c:376
       ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:854

-> #0 (jbd2_handle){++++}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3162 [inline]
       check_prevs_add kernel/locking/lockdep.c:3281 [inline]
       validate_chain kernel/locking/lockdep.c:3897 [inline]
       __lock_acquire+0x3504/0x7280 kernel/locking/lockdep.c:5171
       lock_acquire+0x210/0x63c kernel/locking/lockdep.c:5790
       jbd2_log_wait_commit+0x150/0x438 fs/jbd2/journal.c:694
       ocfs2_try_to_free_truncate_log+0x2c4/0x2f4 fs/ocfs2/alloc.c:6142
       ocfs2_write_begin_nolock+0x2a44/0x3a80 fs/ocfs2/aops.c:1872
       ocfs2_write_begin+0x1b4/0x318 fs/ocfs2/aops.c:1906
       generic_perform_write+0x240/0x508 mm/filemap.c:3862
       __generic_file_write_iter+0x130/0x250 mm/filemap.c:3960
       ocfs2_file_write_iter+0x13ac/0x1cd0 fs/ocfs2/file.c:2469
       call_write_iter include/linux/fs.h:2271 [inline]
       new_sync_write fs/read_write.c:491 [inline]
       vfs_write+0x3c8/0x7c8 fs/read_write.c:584
       ksys_pwrite64 fs/read_write.c:699 [inline]
       __do_sys_pwrite64 fs/read_write.c:709 [inline]
       __se_sys_pwrite64 fs/read_write.c:706 [inline]
       __arm64_sys_pwrite64+0x178/0x210 fs/read_write.c:706
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x12c arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:589

other info that might help us debug this:

Chain exists of:
  jbd2_handle --> &dquot->dq_lock --> &ocfs2_quota_ip_alloc_sem_key

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ocfs2_quota_ip_alloc_sem_key);
                               lock(&dquot->dq_lock);
                               lock(&ocfs2_quota_ip_alloc_sem_key);
  lock(jbd2_handle);

 *** DEADLOCK ***

3 locks held by syz.3.758/6497:
 #0: ffff0000d1f48460 (sb_writers#17){.+.+}-{0:0}, at: vfs_write+0x254/0x7c8 fs/read_write.c:580
 #1: ffff0000e23b9808 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:764 [inline]
 #1: ffff0000e23b9808 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: ocfs2_file_write_iter+0x3ac/0x1cd0 fs/ocfs2/file.c:2399
 #2: ffff0000e23b94a0 (&ocfs2_quota_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_write_begin+0x190/0x318 fs/ocfs2/aops.c:1904

stack backtrace:
CPU: 0 PID: 6497 Comm: syz.3.758 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
Call trace:
 dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2088
 check_noncircular+0x290/0x370 kernel/locking/lockdep.c:2215
 check_prev_add kernel/locking/lockdep.c:3162 [inline]
 check_prevs_add kernel/locking/lockdep.c:3281 [inline]
 validate_chain kernel/locking/lockdep.c:3897 [inline]
 __lock_acquire+0x3504/0x7280 kernel/locking/lockdep.c:5171
 lock_acquire+0x210/0x63c kernel/locking/lockdep.c:5790
 jbd2_log_wait_commit+0x150/0x438 fs/jbd2/journal.c:694
 ocfs2_try_to_free_truncate_log+0x2c4/0x2f4 fs/ocfs2/alloc.c:6142
 ocfs2_write_begin_nolock+0x2a44/0x3a80 fs/ocfs2/aops.c:1872
 ocfs2_write_begin+0x1b4/0x318 fs/ocfs2/aops.c:1906
 generic_perform_write+0x240/0x508 mm/filemap.c:3862
 __generic_file_write_iter+0x130/0x250 mm/filemap.c:3960
 ocfs2_file_write_iter+0x13ac/0x1cd0 fs/ocfs2/file.c:2469
 call_write_iter include/linux/fs.h:2271 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x3c8/0x7c8 fs/read_write.c:584
 ksys_pwrite64 fs/read_write.c:699 [inline]
 __do_sys_pwrite64 fs/read_write.c:709 [inline]
 __se_sys_pwrite64 fs/read_write.c:706 [inline]
 __arm64_sys_pwrite64+0x178/0x210 fs/read_write.c:706
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x12c arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:589

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/18 19:36 linux-6.1.y c75b0cf0982c 2006bdcc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in jbd2_log_wait_commit
* Struck through repros no longer work on HEAD.