syzbot

JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,3) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
5.15.189-syzkaller #0 Not tainted
------------------------------------------------------
syz.3.92/4864 is trying to acquire lock:
ffff88807ac6c028 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0x90/0x110 mm/memory.c:5356

but task is already holding lock:
ffff8880635a5be0 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_fiemap+0x2a2/0xc40 fs/ocfs2/extent_map.c:755

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&oi->ip_alloc_sem){++++}-{3:3}:
       down_write+0x38/0x60 kernel/locking/rwsem.c:1551
       ocfs2_page_mkwrite+0x2ce/0xad0 fs/ocfs2/mmap.c:142
       do_page_mkwrite+0x168/0x3c0 mm/memory.c:2922
       wp_page_shared+0x16b/0x6d0 mm/memory.c:3259
       handle_pte_fault mm/memory.c:4668 [inline]
       __handle_mm_fault mm/memory.c:4785 [inline]
       handle_mm_fault+0x1eca/0x43c0 mm/memory.c:4883
       do_user_addr_fault+0x489/0xc80 arch/x86/mm/fault.c:1357
       handle_page_fault arch/x86/mm/fault.c:1445 [inline]
       exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1501
       asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606

-> #1 (sb_pagefaults#4){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1811 [inline]
       sb_start_pagefault include/linux/fs.h:1910 [inline]
       ocfs2_page_mkwrite+0x18a/0xad0 fs/ocfs2/mmap.c:122
       do_page_mkwrite+0x168/0x3c0 mm/memory.c:2922
       wp_page_shared+0x16b/0x6d0 mm/memory.c:3259
       handle_pte_fault mm/memory.c:4668 [inline]
       __handle_mm_fault mm/memory.c:4785 [inline]
       handle_mm_fault+0x1eca/0x43c0 mm/memory.c:4883
       do_user_addr_fault+0x489/0xc80 arch/x86/mm/fault.c:1357
       handle_page_fault arch/x86/mm/fault.c:1445 [inline]
       exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1501
       asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
       lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
       __might_fault+0xb3/0x110 mm/memory.c:5357
       _copy_to_user+0x29/0x130 lib/usercopy.c:35
       copy_to_user include/linux/uaccess.h:200 [inline]
       fiemap_fill_next_extent+0x19d/0x360 fs/ioctl.c:144
       ocfs2_fiemap+0x857/0xc40 fs/ocfs2/extent_map.c:796
       ioctl_fiemap fs/ioctl.c:219 [inline]
       do_vfs_ioctl+0x1464/0x1de0 fs/ioctl.c:814
       __do_sys_ioctl fs/ioctl.c:872 [inline]
       __se_sys_ioctl+0x83/0x170 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

Chain exists of:
  &mm->mmap_lock --> sb_pagefaults#4 --> &oi->ip_alloc_sem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&oi->ip_alloc_sem);
                               lock(sb_pagefaults#4);
                               lock(&oi->ip_alloc_sem);
  lock(&mm->mmap_lock);

 *** DEADLOCK ***

1 lock held by syz.3.92/4864:
 #0: ffff8880635a5be0 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_fiemap+0x2a2/0xc40 fs/ocfs2/extent_map.c:755

stack backtrace:
CPU: 1 PID: 4864 Comm: syz.3.92 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 __might_fault+0xb3/0x110 mm/memory.c:5357
 _copy_to_user+0x29/0x130 lib/usercopy.c:35
 copy_to_user include/linux/uaccess.h:200 [inline]
 fiemap_fill_next_extent+0x19d/0x360 fs/ioctl.c:144
 ocfs2_fiemap+0x857/0xc40 fs/ocfs2/extent_map.c:796
 ioctl_fiemap fs/ioctl.c:219 [inline]
 do_vfs_ioctl+0x1464/0x1de0 fs/ioctl.c:814
 __do_sys_ioctl fs/ioctl.c:872 [inline]
 __se_sys_ioctl+0x83/0x170 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7ff45d46cbe9
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:00007ff45b6d4038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff45d693fa0 RCX: 00007ff45d46cbe9
RDX: 0000200000000140 RSI: 00000000c020660b RDI: 0000000000000006
RBP: 00007ff45d4efe19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff45d694038 R14: 00007ff45d693fa0 R15: 00007fff7ae8fad8
 </TASK>