possible deadlock in ocfs2_write_begin_nolock

Status: upstream: reported C repro on 2024/10/27 04:30
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+1782a3a587bc53dc10cf@syzkaller.appspotmail.com
First crash: 682d, last: 2d18h
Fix bisection: failed (error log, bisect log)
  
Discussions (1)
Title Replies (including bot) Last reply
[BUG] ocfs2: possible deadlock in ocfs2_write_begin_nolock on v7.2-rc3 3 (3) 2026/09/04 06:57
Bug presence (1)
Date Name Commit Repro Result
2025/12/06 upstream (ToT) 3af870aedbff C [report] possible deadlock in ocfs2_write_begin_nolock
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 possible deadlock in ocfs2_write_begin_nolock (2) 4 3 238d 300d 0/2 auto-obsoleted due to no activity on 2026/04/24 14:52
upstream possible deadlock in ocfs2_write_begin_nolock ocfs2 4 syz, C 1030 107d 727d 0/29 auto-obsoleted due to no activity on 2026/08/03 06:09
linux-6.1 possible deadlock in ocfs2_write_begin_nolock origin:upstream 4 syz, C error 213 40d 698d 0/3 upstream: reported C repro on 2024/10/11 23:44
linux-6.6 possible deadlock in ocfs2_write_begin_nolock 4 3 414d 442d 0/2 auto-obsoleted due to no activity on 2025/10/30 13:30
Last patch testing requests (3)
Created Duration User Patch Repo Result
2026/08/19 15:13 1h36m retest repro linux-5.15.y report job log log
2026/06/09 05:51 16m retest repro linux-5.15.y report log
2026/02/05 21:14 10m retest repro linux-5.15.y report log

Sample crash report:
JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.54/4664 is trying to acquire lock:
ffff88801fbb0650 (sb_internal#2){.+.+}-{0:0}, at: ocfs2_write_begin_inline fs/ocfs2/aops.c:1484 [inline]
ffff88801fbb0650 (sb_internal#2){.+.+}-{0:0}, at: ocfs2_try_to_write_inline_data fs/ocfs2/aops.c:1587 [inline]
ffff88801fbb0650 (sb_internal#2){.+.+}-{0:0}, at: ocfs2_write_begin_nolock+0x207c/0x44b0 fs/ocfs2/aops.c:1673

but task is already holding lock:
ffff88805c5d22e0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_write_begin+0x193/0x310 fs/ocfs2/aops.c:1905

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}:
       down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498
       ocfs2_read_virt_blocks+0x240/0x8e0 fs/ocfs2/extent_map.c:984
       ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline]
       ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline]
       ocfs2_find_entry+0x39d/0x1f90 fs/ocfs2/dir.c:1091
       ocfs2_find_files_on_disk+0xdb/0x2f0 fs/ocfs2/dir.c:1995
       ocfs2_lookup_ino_from_name+0x4f/0xf0 fs/ocfs2/dir.c:2017
       ocfs2_find_victim_alloc_group+0x19e/0x960 fs/ocfs2/move_extents.c:385
       ocfs2_move_extent fs/ocfs2/move_extents.c:658 [inline]
       __ocfs2_move_extents_range+0x1c72/0x3450 fs/ocfs2/move_extents.c:868
       ocfs2_move_extents+0x409/0xa40 fs/ocfs2/move_extents.c:940
       ocfs2_ioctl_move_extents+0x4d7/0x6e0 fs/ocfs2/move_extents.c:1066
       ocfs2_ioctl+0x31f/0x7a0 fs/ocfs2/ioctl.c:947
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #1 (&journal->j_trans_barrier){.+.+}-{3:3}:
       down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498
       ocfs2_start_trans+0x3a6/0x6f0 fs/ocfs2/journal.c:374
       ocfs2_mknod+0xf70/0x2510 fs/ocfs2/namei.c:361
       ocfs2_create+0x192/0x420 fs/ocfs2/namei.c:674
       lookup_open fs/namei.c:3513 [inline]
       open_last_lookups fs/namei.c:3583 [inline]
       path_openat+0x120a/0x2fb0 fs/namei.c:3790
       do_filp_open+0x1df/0x400 fs/namei.c:3820
       do_sys_openat2+0x14b/0x500 fs/open.c:1255
       do_sys_open fs/open.c:1271 [inline]
       __do_sys_openat fs/open.c:1287 [inline]
       __se_sys_openat fs/open.c:1282 [inline]
       __x64_sys_openat+0x135/0x160 fs/open.c:1282
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (sb_internal#2){.+.+}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
       lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1817 [inline]
       sb_start_intwrite include/linux/fs.h:1934 [inline]
       ocfs2_start_trans+0x2a7/0x6f0 fs/ocfs2/journal.c:372
       ocfs2_write_begin_inline fs/ocfs2/aops.c:1484 [inline]
       ocfs2_try_to_write_inline_data fs/ocfs2/aops.c:1587 [inline]
       ocfs2_write_begin_nolock+0x207c/0x44b0 fs/ocfs2/aops.c:1673
       ocfs2_write_begin+0x1b4/0x310 fs/ocfs2/aops.c:1907
       generic_perform_write+0x2b6/0x550 mm/filemap.c:3785
       __generic_file_write_iter+0x261/0x4e0 mm/filemap.c:3912
       ocfs2_file_write_iter+0x171a/0x1ee0 fs/ocfs2/file.c:2472
       call_write_iter include/linux/fs.h:2179 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0x748/0xd70 fs/read_write.c:594
       ksys_write+0x153/0x260 fs/read_write.c:647
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

Chain exists of:
  sb_internal#2 --> &journal->j_trans_barrier --> &ocfs2_file_ip_alloc_sem_key

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ocfs2_file_ip_alloc_sem_key);
                               lock(&journal->j_trans_barrier);
                               lock(&ocfs2_file_ip_alloc_sem_key);
  lock(sb_internal#2);

 *** DEADLOCK ***

3 locks held by syz.0.54/4664:
 #0: ffff88801fbb0460 (sb_writers#13){.+.+}-{0:0}, at: vfs_write+0x296/0xd70 fs/read_write.c:590
 #1: ffff88805c5d2648 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:793 [inline]
 #1: ffff88805c5d2648 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ocfs2_file_write_iter+0x437/0x1ee0 fs/ocfs2/file.c:2402
 #2: ffff88805c5d22e0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_write_begin+0x193/0x310 fs/ocfs2/aops.c:1905

stack backtrace:
CPU: 1 PID: 4664 Comm: syz.0.54 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
 __sb_start_write include/linux/fs.h:1817 [inline]
 sb_start_intwrite include/linux/fs.h:1934 [inline]
 ocfs2_start_trans+0x2a7/0x6f0 fs/ocfs2/journal.c:372
 ocfs2_write_begin_inline fs/ocfs2/aops.c:1484 [inline]
 ocfs2_try_to_write_inline_data fs/ocfs2/aops.c:1587 [inline]
 ocfs2_write_begin_nolock+0x207c/0x44b0 fs/ocfs2/aops.c:1673
 ocfs2_write_begin+0x1b4/0x310 fs/ocfs2/aops.c:1907
 generic_perform_write+0x2b6/0x550 mm/filemap.c:3785
 __generic_file_write_iter+0x261/0x4e0 mm/filemap.c:3912
 ocfs2_file_write_iter+0x171a/0x1ee0 fs/ocfs2/file.c:2472
 call_write_iter include/linux/fs.h:2179 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0x748/0xd70 fs/read_write.c:594
 ksys_write+0x153/0x260 fs/read_write.c:647
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f9e4ee70159
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff783ca108 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f9e4f0f7fa0 RCX: 00007f9e4ee70159
RDX: 0000000000000103 RSI: 0000200000000400 RDI: 0000000000000004
RBP: 00007f9e4ef07024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f9e4f0f7fac R14: 00007f9e4f0f7fa0 R15: 00007f9e4f0f7fa0
 </TASK>

Crashes (146):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/07 08:44 linux-5.15.y 0996e0926f6b 4f7b22a0 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/12/05 17:18 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/07/23 01:29 linux-5.15.y c86c4726e7f0 881ce5c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/05/05 14:27 linux-5.15.y ef251c45f1cd 06e69a27 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/02/24 13:49 linux-5.15.y 3330a8d33e08 96b1aa46 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/01/22 19:07 linux-5.15.y 9eec9a14ee10 82c9c083 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/01/17 07:35 linux-5.15.y 68efe5a6c16a 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/01/17 06:00 linux-5.15.y 68efe5a6c16a 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/01/17 03:52 linux-5.15.y 68efe5a6c16a 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/01/16 17:28 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/01/11 07:45 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/01/08 15:48 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2026/01/02 23:36 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/12/25 23:19 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/12/23 03:47 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/12/21 17:15 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/12/12 21:40 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/12/11 16:20 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/12/09 10:13 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/12/07 06:26 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/12/05 16:36 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/12/01 18:03 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/11/19 00:05 linux-5.15.y cc5ec8769306 ef766cd7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/11/16 12:09 linux-5.15.y cc5ec8769306 f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/11/15 15:43 linux-5.15.y cc5ec8769306 f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/11/12 19:37 linux-5.15.y cc5ec8769306 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/11/12 15:50 linux-5.15.y cc5ec8769306 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/10/31 12:30 linux-5.15.y cc5ec8769306 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/10/22 05:42 linux-5.15.y ac56c046adf4 252fbbad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/10/06 06:17 linux-5.15.y 29e53a5b1c4f 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/08/29 00:53 linux-5.15.y 01879f56bdde d401b9d7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/08/24 23:47 linux-5.15.y c79648372d02 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/07/23 21:53 linux-5.15.y c79648372d02 e1dd4f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/07/18 06:16 linux-5.15.y c79648372d02 88248e14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/07/17 01:29 linux-5.15.y 89950c454265 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/07/16 10:58 linux-5.15.y 89950c454265 124ec9cc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/06/30 19:56 linux-5.15.y 3dea0e7f549e 6e83b42d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/06/26 16:11 linux-5.15.y 1c700860e8bc 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/06/24 19:48 linux-5.15.y 1c700860e8bc 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2024/10/27 04:29 linux-5.15.y 74cdd62cb470 65e8686b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_write_begin_nolock
2025/08/26 22:40 linux-5.15.y c79648372d02 e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/07/30 00:29 linux-5.15.y c79648372d02 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/07/28 16:43 linux-5.15.y c79648372d02 6654ea9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/07/24 12:54 linux-5.15.y c79648372d02 65d60d73 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/07/24 00:39 linux-5.15.y c79648372d02 0c1d6ded .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/07/18 23:38 linux-5.15.y c79648372d02 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/07/14 21:32 linux-5.15.y 89950c454265 d8fc7335 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/07/12 11:51 linux-5.15.y 2f693b607545 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
* Struck through repros no longer work on HEAD.