====================================================== WARNING: possible circular locking dependency detected 6.17.0-rc1-syzkaller-g8f5ae30d69d7 #0 Not tainted ------------------------------------------------------ syz.4.603/9820 is trying to acquire lock: ffff0000d4d49d90 (&mm->mmap_lock){++++}-{4:4}, at: __might_fault+0x9c/0x124 mm/memory.c:6957 but task is already holding lock: ffff0000dd17bf60 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_fiemap+0x26c/0x9c4 fs/ocfs2/extent_map.c:765 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}: down_write+0x50/0xc0 kernel/locking/rwsem.c:1590 ocfs2_try_remove_refcount_tree+0xb4/0x2d8 fs/ocfs2/refcounttree.c:932 ocfs2_xattr_set+0x460/0xe9c fs/ocfs2/xattr.c:3669 ocfs2_set_acl+0x574/0x628 fs/ocfs2/acl.c:254 ocfs2_iop_set_acl+0x190/0x25c fs/ocfs2/acl.c:286 set_posix_acl fs/posix_acl.c:954 [inline] vfs_set_acl+0x70c/0x974 fs/posix_acl.c:1133 do_set_acl+0xc8/0x1a8 fs/posix_acl.c:1278 do_setxattr fs/xattr.c:633 [inline] filename_setxattr+0x268/0x4f8 fs/xattr.c:665 path_setxattrat+0x2e8/0x320 fs/xattr.c:713 __do_sys_setxattr fs/xattr.c:747 [inline] __se_sys_setxattr fs/xattr.c:743 [inline] __arm64_sys_setxattr+0xc0/0xdc fs/xattr.c:743 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 -> #2 (&oi->ip_xattr_sem){++++}-{4:4}: down_read+0x58/0x2f8 kernel/locking/rwsem.c:1537 ocfs2_xattr_get+0xe8/0x220 fs/ocfs2/xattr.c:1338 ocfs2_xattr_security_get+0x40/0x54 fs/ocfs2/xattr.c:7231 __vfs_getxattr+0x394/0x3c0 fs/xattr.c:423 smk_fetch+0xc4/0x150 security/smack/smack_lsm.c:289 smack_d_instantiate+0x53c/0x7a4 security/smack/smack_lsm.c:3606 security_d_instantiate+0x100/0x204 security/security.c:4109 d_instantiate+0x5c/0x9c fs/dcache.c:1961 ocfs2_mknod+0x151c/0x1cf0 fs/ocfs2/namei.c:453 ocfs2_mkdir+0x190/0x474 fs/ocfs2/namei.c:659 vfs_mkdir+0x284/0x424 fs/namei.c:4366 do_mkdirat+0x1f8/0x4c8 fs/namei.c:4399 __do_sys_mkdirat fs/namei.c:4416 [inline] __se_sys_mkdirat fs/namei.c:4414 [inline] __arm64_sys_mkdirat+0x8c/0xa4 fs/namei.c:4414 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 -> #1 (jbd2_handle){++++}-{0:0}: start_this_handle+0xe74/0x10dc fs/jbd2/transaction.c:444 jbd2__journal_start+0x288/0x51c fs/jbd2/transaction.c:501 __ext4_journal_start_sb+0x378/0x88c fs/ext4/ext4_jbd2.c:115 __ext4_journal_start fs/ext4/ext4_jbd2.h:242 [inline] ext4_dirty_inode+0xa0/0x104 fs/ext4/inode.c:6535 __mark_inode_dirty+0x2ac/0x10dc fs/fs-writeback.c:2527 generic_update_time fs/inode.c:2063 [inline] inode_update_time fs/inode.c:2076 [inline] touch_atime+0x440/0x818 fs/inode.c:2148 file_accessed include/linux/fs.h:2663 [inline] ext4_file_mmap_prepare+0x1c8/0x3a4 fs/ext4/file.c:828 vfs_mmap_prepare include/linux/fs.h:2294 [inline] call_mmap_prepare mm/vma.c:2585 [inline] __mmap_region mm/vma.c:2653 [inline] mmap_region+0x934/0x1d20 mm/vma.c:2739 do_mmap+0x968/0xfac mm/mmap.c:558 vm_mmap_pgoff+0x2d8/0x45c mm/util.c:580 ksys_mmap_pgoff+0x394/0x5b8 mm/mmap.c:604 __do_sys_mmap arch/arm64/kernel/sys.c:28 [inline] __se_sys_mmap arch/arm64/kernel/sys.c:21 [inline] __arm64_sys_mmap+0xf8/0x110 arch/arm64/kernel/sys.c:21 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 -> #0 (&mm->mmap_lock){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x1774/0x30a4 kernel/locking/lockdep.c:5237 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868 __might_fault+0xc4/0x124 mm/memory.c:6958 _inline_copy_to_user include/linux/uaccess.h:192 [inline] copy_to_user include/linux/uaccess.h:223 [inline] fiemap_fill_next_extent+0x17c/0x3f0 fs/ioctl.c:145 ocfs2_fiemap_inline fs/ocfs2/extent_map.c:735 [inline] ocfs2_fiemap+0x770/0x9c4 fs/ocfs2/extent_map.c:772 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1140/0x1834 fs/ioctl.c:532 __do_sys_ioctl fs/ioctl.c:596 [inline] __se_sys_ioctl fs/ioctl.c:584 [inline] __arm64_sys_ioctl+0xe4/0x1c4 fs/ioctl.c:584 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 other info that might help us debug this: Chain exists of: &mm->mmap_lock --> &oi->ip_xattr_sem --> &ocfs2_file_ip_alloc_sem_key Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(&ocfs2_file_ip_alloc_sem_key); lock(&oi->ip_xattr_sem); lock(&ocfs2_file_ip_alloc_sem_key); rlock(&mm->mmap_lock); *** DEADLOCK *** 1 lock held by syz.4.603/9820: #0: ffff0000dd17bf60 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_fiemap+0x26c/0x9c4 fs/ocfs2/extent_map.c:765 stack backtrace: CPU: 1 UID: 0 PID: 9820 Comm: syz.4.603 Not tainted 6.17.0-rc1-syzkaller-g8f5ae30d69d7 #0 PREEMPT Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C) __dump_stack+0x30/0x40 lib/dump_stack.c:94 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 print_circular_bug+0x324/0x32c kernel/locking/lockdep.c:2043 check_noncircular+0x154/0x174 kernel/locking/lockdep.c:2175 check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x1774/0x30a4 kernel/locking/lockdep.c:5237 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868 __might_fault+0xc4/0x124 mm/memory.c:6958 _inline_copy_to_user include/linux/uaccess.h:192 [inline] copy_to_user include/linux/uaccess.h:223 [inline] fiemap_fill_next_extent+0x17c/0x3f0 fs/ioctl.c:145 ocfs2_fiemap_inline fs/ocfs2/extent_map.c:735 [inline] ocfs2_fiemap+0x770/0x9c4 fs/ocfs2/extent_map.c:772 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1140/0x1834 fs/ioctl.c:532 __do_sys_ioctl fs/ioctl.c:596 [inline] __se_sys_ioctl fs/ioctl.c:584 [inline] __arm64_sys_ioctl+0xe4/0x1c4 fs/ioctl.c:584 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596