====================================================== WARNING: possible circular locking dependency detected 6.13.0-rc7-syzkaller-00149-g9bffa1ad25b8 #0 Not tainted ------------------------------------------------------ syz.7.615/7807 is trying to acquire lock: ffff88805745bf60 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_page_mkwrite+0x2cb/0xda0 fs/ocfs2/mmap.c:142 but task is already holding lock: ffff8880256bc518 (sb_pagefaults#4){.+.+}-{0:0}, at: do_page_mkwrite+0x17a/0x380 mm/memory.c:3176 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_pagefaults#4){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1725 [inline] sb_start_pagefault include/linux/fs.h:1890 [inline] ocfs2_page_mkwrite+0x188/0xda0 fs/ocfs2/mmap.c:122 do_page_mkwrite+0x17a/0x380 mm/memory.c:3176 wp_page_shared mm/memory.c:3577 [inline] do_wp_page+0xc4b/0x4670 mm/memory.c:3727 handle_pte_fault mm/memory.c:5817 [inline] __handle_mm_fault+0x1ade/0x2a40 mm/memory.c:5944 handle_mm_fault+0x3fa/0xaa0 mm/memory.c:6112 do_user_addr_fault+0x7a3/0x13f0 arch/x86/mm/fault.c:1389 handle_page_fault arch/x86/mm/fault.c:1481 [inline] exc_page_fault+0x5c/0xc0 arch/x86/mm/fault.c:1539 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 -> #1 (&mm->mmap_lock){++++}-{4:4}: __might_fault mm/memory.c:6751 [inline] __might_fault+0x11b/0x190 mm/memory.c:6744 _inline_copy_to_user include/linux/uaccess.h:192 [inline] _copy_to_user+0x2d/0xd0 lib/usercopy.c:26 copy_to_user include/linux/uaccess.h:225 [inline] fiemap_fill_next_extent+0x232/0x390 fs/ioctl.c:145 ocfs2_fiemap+0x67c/0xd00 fs/ocfs2/extent_map.c:796 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x405/0x1990 fs/ioctl.c:840 __do_sys_ioctl fs/ioctl.c:904 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __x64_sys_ioctl+0x11d/0x200 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5226 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849 down_write+0x93/0x200 kernel/locking/rwsem.c:1577 ocfs2_page_mkwrite+0x2cb/0xda0 fs/ocfs2/mmap.c:142 do_page_mkwrite+0x17a/0x380 mm/memory.c:3176 wp_page_shared mm/memory.c:3577 [inline] do_wp_page+0xc4b/0x4670 mm/memory.c:3727 handle_pte_fault mm/memory.c:5817 [inline] __handle_mm_fault+0x1ade/0x2a40 mm/memory.c:5944 handle_mm_fault+0x3fa/0xaa0 mm/memory.c:6112 do_user_addr_fault+0x7a3/0x13f0 arch/x86/mm/fault.c:1389 handle_page_fault arch/x86/mm/fault.c:1481 [inline] exc_page_fault+0x5c/0xc0 arch/x86/mm/fault.c:1539 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 other info that might help us debug this: Chain exists of: &ocfs2_file_ip_alloc_sem_key --> &mm->mmap_lock --> sb_pagefaults#4 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(sb_pagefaults#4); lock(&mm->mmap_lock); lock(sb_pagefaults#4); lock(&ocfs2_file_ip_alloc_sem_key); *** DEADLOCK *** 2 locks held by syz.7.615/7807: #0: ffff88807f9ce360 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_trylock include/linux/mmap_lock.h:163 [inline] #0: ffff88807f9ce360 (&mm->mmap_lock){++++}-{4:4}, at: get_mmap_lock_carefully mm/memory.c:6149 [inline] #0: ffff88807f9ce360 (&mm->mmap_lock){++++}-{4:4}, at: lock_mm_and_find_vma+0x35/0x6a0 mm/memory.c:6209 #1: ffff8880256bc518 (sb_pagefaults#4){.+.+}-{0:0}, at: do_page_mkwrite+0x17a/0x380 mm/memory.c:3176 stack backtrace: CPU: 0 UID: 0 PID: 7807 Comm: syz.7.615 Not tainted 6.13.0-rc7-syzkaller-00149-g9bffa1ad25b8 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x419/0x5d0 kernel/locking/lockdep.c:2074 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5226 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849 down_write+0x93/0x200 kernel/locking/rwsem.c:1577 ocfs2_page_mkwrite+0x2cb/0xda0 fs/ocfs2/mmap.c:142 do_page_mkwrite+0x17a/0x380 mm/memory.c:3176 wp_page_shared mm/memory.c:3577 [inline] do_wp_page+0xc4b/0x4670 mm/memory.c:3727 handle_pte_fault mm/memory.c:5817 [inline] __handle_mm_fault+0x1ade/0x2a40 mm/memory.c:5944 handle_mm_fault+0x3fa/0xaa0 mm/memory.c:6112 do_user_addr_fault+0x7a3/0x13f0 arch/x86/mm/fault.c:1389 handle_page_fault arch/x86/mm/fault.c:1481 [inline] exc_page_fault+0x5c/0xc0 arch/x86/mm/fault.c:1539 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0033:0x7fc604f4d308 Code: fc 89 37 c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 66 0f 1f 84 00 00 00 00 00 48 8b 4c 16 f8 48 8b 36 <48> 89 37 48 89 4c 17 f8 c3 c5 fe 6f 54 16 e0 c5 fe 6f 5c 16 c0 c5 RSP: 002b:00007ffda47e7248 EFLAGS: 00010246 RAX: 0000000020000200 RBX: 0000000000000004 RCX: 0030656c69662f2e RDX: 0000000000000008 RSI: 0030656c69662f2e RDI: 0000000020000200 RBP: 00007fc605177ba0 R08: 00007fc604e00000 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000000009 R12: 000000000003ea85 R13: 00007fc605175fa0 R14: 0000000000000032 R15: fffffffffffffffe