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.1174/8665 is trying to acquire lock: ffff88807b41a650 (sb_internal#3){.+.+}-{0:0}, at: ocfs2_setattr+0xaa6/0x1cf0 fs/ocfs2/file.c:1263 but task is already holding lock: ffff888054710660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_setattr+0xa97/0x1cf0 fs/ocfs2/file.c:1262 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}: down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x265/0x950 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+0x3d1/0x20c0 fs/ocfs2/dir.c:1091 ocfs2_rename+0x1e13/0x3820 fs/ocfs2/namei.c:1568 vfs_rename+0xbbf/0x10d0 fs/namei.c:4874 do_renameat2+0x89d/0xc70 fs/namei.c:5027 __do_sys_renameat2 fs/namei.c:5060 [inline] __se_sys_renameat2 fs/namei.c:5057 [inline] __x64_sys_renameat2+0xce/0xe0 fs/namei.c:5057 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #2 (jbd2_handle){++++}-{0:0}: start_this_handle+0x1f49/0x2150 fs/jbd2/transaction.c:463 jbd2__journal_start+0x2b7/0x5a0 fs/jbd2/transaction.c:520 jbd2_journal_start+0x26/0x30 fs/jbd2/transaction.c:559 ocfs2_start_trans+0x372/0x6c0 fs/ocfs2/journal.c:376 ocfs2_mknod+0xe6a/0x2350 fs/ocfs2/namei.c:361 ocfs2_create+0x1b6/0x4a0 fs/ocfs2/namei.c:674 vfs_create+0x2db/0x460 fs/namei.c:3184 do_mknodat+0x399/0x4c0 fs/namei.c:4035 __do_sys_mknodat fs/namei.c:4063 [inline] __se_sys_mknodat fs/namei.c:4060 [inline] __x64_sys_mknodat+0xa5/0xc0 fs/namei.c:4060 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 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+0x366/0x6c0 fs/ocfs2/journal.c:374 ocfs2_mknod+0xe6a/0x2350 fs/ocfs2/namei.c:361 ocfs2_create+0x1b6/0x4a0 fs/ocfs2/namei.c:674 vfs_create+0x2db/0x460 fs/namei.c:3184 do_mknodat+0x399/0x4c0 fs/namei.c:4035 __do_sys_mknodat fs/namei.c:4063 [inline] __se_sys_mknodat fs/namei.c:4060 [inline] __x64_sys_mknodat+0xa5/0xc0 fs/namei.c:4060 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (sb_internal#3){.+.+}-{0:0}: 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+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1891 [inline] sb_start_intwrite include/linux/fs.h:2013 [inline] ocfs2_start_trans+0x267/0x6c0 fs/ocfs2/journal.c:372 ocfs2_setattr+0xaa6/0x1cf0 fs/ocfs2/file.c:1263 notify_change+0xc74/0xf40 fs/attr.c:499 do_truncate+0x197/0x220 fs/open.c:65 vfs_truncate+0x262/0x2f0 fs/open.c:111 do_sys_truncate+0xdc/0x190 fs/open.c:134 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 other info that might help us debug this: Chain exists of: sb_internal#3 --> jbd2_handle --> &ocfs2_file_ip_alloc_sem_key Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ocfs2_file_ip_alloc_sem_key); lock(jbd2_handle); lock(&ocfs2_file_ip_alloc_sem_key); lock(sb_internal#3); *** DEADLOCK *** 3 locks held by syz.3.1174/8665: #0: ffff88807b41a460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:393 #1: ffff8880547109c8 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #1: ffff8880547109c8 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}, at: do_truncate+0x183/0x220 fs/open.c:63 #2: ffff888054710660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_setattr+0xa97/0x1cf0 fs/ocfs2/file.c:1262 stack backtrace: CPU: 1 PID: 8665 Comm: syz.3.1174 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106 check_noncircular+0x274/0x310 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+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1891 [inline] sb_start_intwrite include/linux/fs.h:2013 [inline] ocfs2_start_trans+0x267/0x6c0 fs/ocfs2/journal.c:372 ocfs2_setattr+0xaa6/0x1cf0 fs/ocfs2/file.c:1263 notify_change+0xc74/0xf40 fs/attr.c:499 do_truncate+0x197/0x220 fs/open.c:65 vfs_truncate+0x262/0x2f0 fs/open.c:111 do_sys_truncate+0xdc/0x190 fs/open.c:134 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7ff1bd98eec9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ff1be809038 EFLAGS: 00000246 ORIG_RAX: 000000000000004c RAX: ffffffffffffffda RBX: 00007ff1bdbe5fa0 RCX: 00007ff1bd98eec9 RDX: 0000000000000000 RSI: 0000000000040006 RDI: 0000200000000040 RBP: 00007ff1bda11f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ff1bdbe6038 R14: 00007ff1bdbe5fa0 R15: 00007ffdd30728b8