possible deadlock in ocfs2_write_begin_nolock

Status: upstream: reported C repro on 2024/10/11 23:44
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+13376da5d4f789911f90@syzkaller.appspotmail.com
First crash: 770d, last: 4d14h
Fix bisection: failed (error log, bisect log)
▶ ▼ Bug presence (2)
Date Name Commit Repro Result
2026/01/06 upstream (ToT) 7f98ab9da046 C [report] possible deadlock in ocfs2_write_begin_nolock
2026/10/16 upstream (ToT) 2f2f7eeef8b0 C Didn't crash
▶ ▼ 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 311d 372d 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 180d 800d 0/29 auto-obsoleted due to no activity on 2026/08/03 06:09
linux-6.6 possible deadlock in ocfs2_write_begin_nolock 4 3 487d 515d 0/2 auto-obsoleted due to no activity on 2025/10/30 13:30
linux-5.15 possible deadlock in ocfs2_write_begin_nolock origin:upstream 4 syz, C error 146 47d 755d 0/3 upstream: reported C repro on 2024/10/27 04:30

Sample crash report:
ocfs2: Mounting device (7,5) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.5.565/6053 is trying to acquire lock:
ffff88807c230650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_write_begin_inline fs/ocfs2/aops.c:1483 [inline]
ffff88807c230650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_try_to_write_inline_data fs/ocfs2/aops.c:1586 [inline]
ffff88807c230650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_write_begin_nolock+0x20c2/0x4590 fs/ocfs2/aops.c:1672

but task is already holding lock:
ffff888052cd5be0 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_write_begin+0x194/0x310 fs/ocfs2/aops.c:1904

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&oi->ip_alloc_sem){++++}-{3:3}:
       down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
       ocfs2_read_virt_blocks+0x266/0x980 fs/ocfs2/extent_map.c:984
       ocfs2_read_dir_block+0xd1/0x4f0 fs/ocfs2/dir.c:508
       ocfs2_dir_foreach_blk_el fs/ocfs2/dir.c:1903 [inline]
       ocfs2_dir_foreach_blk+0x274/0x1a80 fs/ocfs2/dir.c:1989
       ocfs2_dir_foreach+0x16d/0x1c0 fs/ocfs2/dir.c:1999
       ocfs2_empty_dir+0x105/0x650 fs/ocfs2/dir.c:2217
       ocfs2_rename+0x21d3/0x3a20 fs/ocfs2/namei.c:1500
       vfs_rename+0xd57/0x10f0 fs/namei.c:4929
       do_renameat2+0x8ac/0xc80 fs/namei.c:5082
       __do_sys_renameat2 fs/namei.c:5115 [inline]
       __se_sys_renameat2 fs/namei.c:5112 [inline]
       __x64_sys_renameat2+0xce/0xe0 fs/namei.c:5112
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (&journal->j_trans_barrier){.+.+}-{3:3}:
       down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
       ocfs2_start_trans+0x3a4/0x6f0 fs/ocfs2/journal.c:374
       ocfs2_local_alloc_slide_window fs/ocfs2/localalloc.c:1258 [inline]
       ocfs2_reserve_local_alloc_bits+0xaad/0x2770 fs/ocfs2/localalloc.c:668
       ocfs2_reserve_clusters_with_limit+0x1b6/0xc10 fs/ocfs2/suballoc.c:1184
       ocfs2_mknod+0x1204/0x2500 fs/ocfs2/namei.c:354
       ocfs2_mkdir+0x1b6/0x4b0 fs/ocfs2/namei.c:659
       vfs_mkdir+0x386/0x570 fs/namei.c:4161
       do_mkdirat+0x1d8/0x440 fs/namei.c:4186
       __do_sys_mkdirat fs/namei.c:4201 [inline]
       __se_sys_mkdirat fs/namei.c:4199 [inline]
       __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4199
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (sb_internal#4){.+.+}-{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+0x3a03/0x7ea0 kernel/locking/lockdep.c:5171
       lock_acquire+0x1bc/0x4a0 kernel/locking/lockdep.c:5790
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1897 [inline]
       sb_start_intwrite include/linux/fs.h:2019 [inline]
       ocfs2_start_trans+0x2a5/0x6f0 fs/ocfs2/journal.c:372
       ocfs2_write_begin_inline fs/ocfs2/aops.c:1483 [inline]
       ocfs2_try_to_write_inline_data fs/ocfs2/aops.c:1586 [inline]
       ocfs2_write_begin_nolock+0x20c2/0x4590 fs/ocfs2/aops.c:1672
       ocfs2_write_begin+0x1b7/0x310 fs/ocfs2/aops.c:1906
       generic_perform_write+0x2fa/0x5c0 mm/filemap.c:3862
       __generic_file_write_iter+0x148/0x2a0 mm/filemap.c:3960
       ocfs2_file_write_iter+0x1731/0x1fc0 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+0x482/0x9a0 fs/read_write.c:584
       ksys_write+0x14d/0x260 fs/read_write.c:637
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

Chain exists of:
  sb_internal#4 --> &journal->j_trans_barrier --> &oi->ip_alloc_sem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&oi->ip_alloc_sem);
                               lock(&journal->j_trans_barrier);
                               lock(&oi->ip_alloc_sem);
  rlock(sb_internal#4);

 *** DEADLOCK ***

4 locks held by syz.5.565/6053:
 #0: ffff888030fa4d68 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
 #1: ffff88807c230460 (sb_writers#25){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
 #2: ffff888052cd5f48 (&sb->s_type->i_mutex_key#33){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:764 [inline]
 #2: ffff888052cd5f48 (&sb->s_type->i_mutex_key#33){+.+.}-{3:3}, at: ocfs2_file_write_iter+0x45a/0x1fc0 fs/ocfs2/file.c:2399
 #3: ffff888052cd5be0 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_write_begin+0x194/0x310 fs/ocfs2/aops.c:1904

stack backtrace:
CPU: 0 PID: 6053 Comm: syz.5.565 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 check_noncircular+0x2f8/0x400 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+0x3a03/0x7ea0 kernel/locking/lockdep.c:5171
 lock_acquire+0x1bc/0x4a0 kernel/locking/lockdep.c:5790
 percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
 __sb_start_write include/linux/fs.h:1897 [inline]
 sb_start_intwrite include/linux/fs.h:2019 [inline]
 ocfs2_start_trans+0x2a5/0x6f0 fs/ocfs2/journal.c:372
 ocfs2_write_begin_inline fs/ocfs2/aops.c:1483 [inline]
 ocfs2_try_to_write_inline_data fs/ocfs2/aops.c:1586 [inline]
 ocfs2_write_begin_nolock+0x20c2/0x4590 fs/ocfs2/aops.c:1672
 ocfs2_write_begin+0x1b7/0x310 fs/ocfs2/aops.c:1906
 generic_perform_write+0x2fa/0x5c0 mm/filemap.c:3862
 __generic_file_write_iter+0x148/0x2a0 mm/filemap.c:3960
 ocfs2_file_write_iter+0x1731/0x1fc0 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+0x482/0x9a0 fs/read_write.c:584
 ksys_write+0x14d/0x260 fs/read_write.c:637
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc1ad5a94d9
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:00007fc1ae4fe028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fc1ad825fa0 RCX: 00007fc1ad5a94d9
RDX: 0000000000000020 RSI: 0000200000008fc0 RDI: 0000000000000004
RBP: 00007fc1ad63804e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc1ad826038 R14: 00007fc1ad825fa0 R15: 00007ffd8a8448a8
 </TASK>

Crashes (220):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/16 10:23 linux-6.1.y c75b0cf0982c 31830773 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2026/04/08 03:13 linux-6.1.y 1989cd3d56e2 2c961e87 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2026/04/07 12:17 linux-6.1.y 1989cd3d56e2 628666c6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2026/04/01 13:08 linux-6.1.y 1989cd3d56e2 9a1f7828 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2026/03/31 12:13 linux-6.1.y 1989cd3d56e2 aeea1c72 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2026/03/30 12:54 linux-6.1.y 1989cd3d56e2 dcaebc52 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2026/03/22 18:13 linux-6.1.y f2ddafa93a25 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2025/11/03 23:27 linux-6.1.y f6e38ae624cf 686bf657 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2025/10/31 18:11 linux-6.1.y f6e38ae624cf 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2025/10/23 00:31 linux-6.1.y 8e6e2188d949 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2025/09/22 10:48 linux-6.1.y 363a599da6d9 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_write_begin_nolock
2026/11/17 00:17 linux-6.1.y c75b0cf0982c a3e64cfc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/11/15 08:41 linux-6.1.y c75b0cf0982c 819ebe34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/10/14 07:38 linux-6.1.y a500ba24937a 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/07/31 16:24 linux-6.1.y fb28aa725e05 7664cf44 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/07/30 15:26 linux-6.1.y fb28aa725e05 2377cd3d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/07/29 22:36 linux-6.1.y 1016ca6176ee 6ef5c1e2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/07/24 19:15 linux-6.1.y dc5c83b7f5f8 dd737a83 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/07/22 14:54 linux-6.1.y 090666d3cc90 4a865b71 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/06/23 18:11 linux-6.1.y fdb6fcb41cc7 4b1d8f01 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/06/19 10:50 linux-6.1.y 228da13e907e 570c59ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/06/17 03:13 linux-6.1.y 228da13e907e 62cc6db3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/06/12 19:42 linux-6.1.y 228da13e907e 1d2f3589 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/02/22 17:44 linux-6.1.y 779f9571ac3e 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/02/20 10:08 linux-6.1.y 779f9571ac3e 17d780d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/02/18 17:54 linux-6.1.y 8ce36b2849ef 77d4d919 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/02/17 04:59 linux-6.1.y 8ce36b2849ef e439b951 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/02/13 19:04 linux-6.1.y 8ce36b2849ef 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/02/12 21:46 linux-6.1.y 8ce36b2849ef 504cb1bf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/02/07 03:45 linux-6.1.y 0182cb5b74ee f20fc9f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/02/06 19:57 linux-6.1.y 0182cb5b74ee 97745f52 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/02/06 00:39 linux-6.1.y cd9b81672742 f03c4191 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/02/05 15:31 linux-6.1.y cd9b81672742 4936e85c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/01/18 03:39 linux-6.1.y cd9b81672742 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/01/17 06:46 linux-6.1.y bec0e10ee67e 20d37d28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/01/15 01:45 linux-6.1.y bec0e10ee67e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/01/07 05:54 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/01/05 04:37 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2026/01/05 03:01 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/12/31 18:02 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/12/23 18:36 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/12/21 16:23 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/12/20 00:55 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/12/15 14:09 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/12/13 19:38 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/12/11 18:00 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/12/05 14:52 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/11/02 16:41 linux-6.1.y f6e38ae624cf 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/10/19 21:23 linux-6.1.y 8e6e2188d949 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/10/18 02:30 linux-6.1.y c2fda4b3f577 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/10/15 21:23 linux-6.1.y c2fda4b3f577 19568248 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/09/27 05:39 linux-6.1.y 7b34dc04e4ff 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/09/19 22:07 linux-6.1.y 363a599da6d9 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/09/04 22:23 linux-6.1.y 28c695c365e1 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/09/02 18:32 linux-6.1.y f89b6e15694c 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2025/08/22 10:08 linux-6.1.y 0bc96de781b4 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
2024/10/11 23:44 linux-6.1.y aa4cd140bba5 084d8178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_write_begin_nolock
* Struck through repros no longer work on HEAD.