ocfs2: Mounting device (7,8) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.8.277/8014 is trying to acquire lock:
ffff88803a26a220 (&mm->mmap_lock){++++}-{4:4}, at: __might_fault+0xb0/0x130

but task is already holding lock:
ffff88811a688660 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_fiemap+0x2b0/0xc90

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}:
       lock_acquire+0x120/0x360
       down_read+0x46/0x2e0
       ocfs2_read_folio+0x353/0x970
       filemap_read_folio+0x117/0x380
       filemap_get_pages+0xd4e/0x1ea0
       filemap_read+0x3f6/0x11a0
       ocfs2_file_read_iter+0x3fa/0xa80
       __kernel_read+0x4cf/0x960
       integrity_kernel_read+0x89/0xd0
       ima_calc_file_hash+0x85e/0x16f0
       ima_collect_measurement+0x428/0x8e0
       process_measurement+0x1121/0x1a40
       ima_file_check+0xd7/0x120
       security_file_post_open+0xbb/0x290
       path_openat+0x2f26/0x3830
       do_filp_open+0x1fa/0x410
       do_sys_openat2+0x121/0x1c0
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (mapping.invalidate_lock#6){.+.+}-{4:4}:
       lock_acquire+0x120/0x360
       down_read+0x46/0x2e0
       filemap_fault+0x548/0x1200
       ocfs2_fault+0xa4/0x3f0
       __do_fault+0x138/0x390
       __handle_mm_fault+0x3611/0x5440
       handle_mm_fault+0x40a/0x8e0
       do_user_addr_fault+0x764/0x1390
       exc_page_fault+0x76/0xf0
       asm_exc_page_fault+0x26/0x30
       fault_in_readable+0x8e/0x130
       fault_in_iov_iter_readable+0x1b4/0x2f0
       generic_perform_write+0x7b5/0x900
       __generic_file_write_iter+0x1ae/0x230
       ocfs2_file_write_iter+0x157a/0x1d10
       do_iter_readv_writev+0x61c/0x8b0
       vfs_writev+0x31a/0x960
       __se_sys_pwritev2+0x179/0x290
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&mm->mmap_lock){++++}-{4:4}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       lock_acquire+0x120/0x360
       __might_fault+0xcc/0x130
       _copy_to_user+0x2c/0xb0
       fiemap_fill_next_extent+0x1c0/0x390
       ocfs2_fiemap+0x9dc/0xc90
       do_vfs_ioctl+0x1173/0x1430
       __se_sys_ioctl+0x82/0x170
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &mm->mmap_lock --> mapping.invalidate_lock#6 --> &ocfs2_file_ip_alloc_sem_key

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(&ocfs2_file_ip_alloc_sem_key);
                               lock(mapping.invalidate_lock#6);
                               lock(&ocfs2_file_ip_alloc_sem_key);
  rlock(&mm->mmap_lock);

 *** DEADLOCK ***

1 lock held by syz.8.277/8014:
 #0: ffff88811a688660 (&ocfs2_file_ip_alloc_sem_key){++++}-{4:4}, at: ocfs2_fiemap+0x2b0/0xc90

stack backtrace:
CPU: 0 UID: 0 PID: 8014 Comm: syz.8.277 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250
 print_circular_bug+0x2ee/0x310
 check_noncircular+0x134/0x160
 validate_chain+0xb9b/0x2140
 __lock_acquire+0xab9/0xd20
 lock_acquire+0x120/0x360
 __might_fault+0xcc/0x130
 _copy_to_user+0x2c/0xb0
 fiemap_fill_next_extent+0x1c0/0x390
 ocfs2_fiemap+0x9dc/0xc90
 do_vfs_ioctl+0x1173/0x1430
 __se_sys_ioctl+0x82/0x170
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f6fbed8ebe9
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:00007f6fbcff6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f6fbefb5fa0 RCX: 00007f6fbed8ebe9
RDX: 0000200000000040 RSI: 00000000c020660b RDI: 0000000000000006
RBP: 00007f6fbee11e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f6fbefb6038 R14: 00007f6fbefb5fa0 R15: 00007ffec7014ed8
 </TASK>
