====================================================== WARNING: possible circular locking dependency detected 6.1.141-syzkaller #0 Not tainted ------------------------------------------------------ syz.1.792/6387 is trying to acquire lock: ffff0000e1b2d108 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#5){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] ffff0000e1b2d108 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#5){+.+.}-{3:3}, at: __ocfs2_flush_truncate_log+0x2dc/0x1068 fs/ocfs2/alloc.c:6047 but task is already holding lock: ffff0000e1a33488 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] ffff0000e1a33488 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6){+.+.}-{3:3}, at: ocfs2_flush_truncate_log fs/ocfs2/alloc.c:6076 [inline] ffff0000e1a33488 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6){+.+.}-{3:3}, at: ocfs2_try_to_free_truncate_log+0x160/0x2d8 fs/ocfs2/alloc.c:6136 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6){+.+.}-{3:3}: down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ocfs2_move_extent fs/ocfs2/move_extents.c:640 [inline] __ocfs2_move_extents_range+0x1380/0x2aac fs/ocfs2/move_extents.c:860 ocfs2_move_extents+0x314/0x7e0 fs/ocfs2/move_extents.c:927 ocfs2_ioctl_move_extents+0x3fc/0x5c8 fs/ocfs2/move_extents.c:1053 ocfs2_ioctl+0x204/0xaf4 fs/ocfs2/ioctl.c:930 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 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:585 -> #0 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#5){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x293c/0x6544 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] __ocfs2_flush_truncate_log+0x2dc/0x1068 fs/ocfs2/alloc.c:6047 ocfs2_flush_truncate_log fs/ocfs2/alloc.c:6077 [inline] ocfs2_try_to_free_truncate_log+0x168/0x2d8 fs/ocfs2/alloc.c:6136 ocfs2_write_begin_nolock+0x28a8/0x3ab4 fs/ocfs2/aops.c:1870 ocfs2_write_begin+0x1b4/0x30c fs/ocfs2/aops.c:1904 generic_perform_write+0x230/0x4b0 mm/filemap.c:3846 __generic_file_write_iter+0x168/0x37c mm/filemap.c:3974 ocfs2_file_write_iter+0x1300/0x1bf4 fs/ocfs2/file.c:2469 __kernel_write_iter+0x200/0x558 fs/read_write.c:517 dump_emit_page fs/coredump.c:950 [inline] dump_user_range+0x318/0x5e8 fs/coredump.c:977 elf_core_dump+0x27bc/0x2cc4 fs/binfmt_elf.c:2354 do_coredump+0x10c4/0x1c4c fs/coredump.c:824 get_signal+0xdec/0x1310 kernel/signal.c:2857 do_signal arch/arm64/kernel/signal.c:1081 [inline] do_notify_resume+0x290/0x2b0c arch/arm64/kernel/signal.c:1134 prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline] exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline] el0_da+0xb4/0x154 arch/arm64/kernel/entry-common.c:516 el0t_64_sync_handler+0x90/0xf0 arch/arm64/kernel/entry-common.c:658 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6); lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#5); lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6); lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#5); *** DEADLOCK *** 4 locks held by syz.1.792/6387: #0: ffff000104e2c460 (sb_writers#14){.+.+}-{0:0}, at: do_coredump+0x109c/0x1c4c fs/coredump.c:823 #1: ffff0000dff709c8 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #1: ffff0000dff709c8 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: ocfs2_file_write_iter+0x3a4/0x1bf4 fs/ocfs2/file.c:2399 #2: ffff0000dff70660 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_write_begin+0x190/0x30c fs/ocfs2/aops.c:1902 #3: ffff0000e1a33488 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #3: ffff0000e1a33488 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6){+.+.}-{3:3}, at: ocfs2_flush_truncate_log fs/ocfs2/alloc.c:6076 [inline] #3: ffff0000e1a33488 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6){+.+.}-{3:3}, at: ocfs2_try_to_free_truncate_log+0x160/0x2d8 fs/ocfs2/alloc.c:6136 stack backtrace: CPU: 1 PID: 6387 Comm: syz.1.792 Not tainted 6.1.141-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call trace: dump_backtrace+0x1c8/0x1f4 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+0xf8/0x160 lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2048 check_noncircular+0x240/0x2d4 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x293c/0x6544 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] __ocfs2_flush_truncate_log+0x2dc/0x1068 fs/ocfs2/alloc.c:6047 ocfs2_flush_truncate_log fs/ocfs2/alloc.c:6077 [inline] ocfs2_try_to_free_truncate_log+0x168/0x2d8 fs/ocfs2/alloc.c:6136 ocfs2_write_begin_nolock+0x28a8/0x3ab4 fs/ocfs2/aops.c:1870 ocfs2_write_begin+0x1b4/0x30c fs/ocfs2/aops.c:1904 generic_perform_write+0x230/0x4b0 mm/filemap.c:3846 __generic_file_write_iter+0x168/0x37c mm/filemap.c:3974 ocfs2_file_write_iter+0x1300/0x1bf4 fs/ocfs2/file.c:2469 __kernel_write_iter+0x200/0x558 fs/read_write.c:517 dump_emit_page fs/coredump.c:950 [inline] dump_user_range+0x318/0x5e8 fs/coredump.c:977 elf_core_dump+0x27bc/0x2cc4 fs/binfmt_elf.c:2354 do_coredump+0x10c4/0x1c4c fs/coredump.c:824 get_signal+0xdec/0x1310 kernel/signal.c:2857 do_signal arch/arm64/kernel/signal.c:1081 [inline] do_notify_resume+0x290/0x2b0c arch/arm64/kernel/signal.c:1134 prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline] exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline] el0_da+0xb4/0x154 arch/arm64/kernel/entry-common.c:516 el0t_64_sync_handler+0x90/0xf0 arch/arm64/kernel/entry-common.c:658 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 (syz.1.792,6387,1):ocfs2_inode_is_valid_to_delete:872 ERROR: Skipping delete of system file 72 ocfs2: Unmounting device (7,1) on (node local)