EXT4-fs (loop5): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none.
======================================================
WARNING: possible circular locking dependency detected
6.16.0-rc4-syzkaller-00286-gc435a4f487e8-dirty #0 Not tainted
------------------------------------------------------
syz.5.2044/11582 is trying to acquire lock:
ffff88801dc280c8 (&ei->xattr_sem){++++}-{4:4}, at: ext4_readpage_inline+0x36/0x6a0

but task is already holding lock:
ffff88801dc28580 (mapping.invalidate_lock#2){++++}-{4:4}, at: filemap_get_pages+0xc29/0x1ea0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (mapping.invalidate_lock#2){++++}-{4:4}:
       lock_acquire+0x120/0x360
       down_read+0x46/0x2e0
       page_cache_ra_unbounded+0x129/0x7b0
       filemap_fault+0x59e/0x1200
       __do_fault+0x138/0x390
       __handle_mm_fault+0x37ed/0x5620
       handle_mm_fault+0x40a/0x8e0
       __get_user_pages+0x1af4/0x30b0
       get_dump_page+0x1ac/0x3f0
       dump_user_range+0x1de/0xc70
       elf_core_dump+0x32ed/0x3900
       do_coredump+0x2809/0x3440
       get_signal+0x1109/0x1340
       arch_do_signal_or_restart+0x9a/0x750
       irqentry_exit_to_user_mode+0x81/0x120
       exc_page_fault+0x9f/0xf0
       asm_exc_page_fault+0x26/0x30

-> #3 (&mm->mmap_lock){++++}-{4:4}:
       lock_acquire+0x120/0x360
       __might_fault+0xcc/0x130
       _copy_to_user+0x2c/0xb0
       fiemap_fill_next_extent+0x1c0/0x390
       ocfs2_fiemap+0x888/0xc90
       do_vfs_ioctl+0x16d3/0x1990
       __se_sys_ioctl+0x82/0x170
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&ocfs2_quota_ip_alloc_sem_key){++++}-{4:4}:
       lock_acquire+0x120/0x360
       down_write+0x96/0x1f0
       ocfs2_create_local_dquot+0x19d/0x1a40
       ocfs2_acquire_dquot+0x80f/0xb30
       dqget+0x7b1/0xf10
       dquot_set_dqblk+0x2b/0xfa0
       quota_setquota+0x4b7/0x540
       __se_sys_quotactl+0x279/0x950
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&dquot->dq_lock){+.+.}-{4:4}:
       lock_acquire+0x120/0x360
       __mutex_lock+0x182/0xe80
       dqget+0x72a/0xf10
       dquot_transfer+0x4b8/0x6d0
       ext4_setattr+0x865/0x1bc0
       notify_change+0xb36/0xe40
       chown_common+0x40c/0x5c0
       do_fchownat+0x161/0x270
       __x64_sys_lchown+0x85/0xa0
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ei->xattr_sem){++++}-{4:4}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       lock_acquire+0x120/0x360
       down_read+0x46/0x2e0
       ext4_readpage_inline+0x36/0x6a0
       ext4_read_folio+0x16c/0x320
       filemap_read_folio+0x117/0x380
       filemap_get_pages+0xd4e/0x1ea0
       filemap_read+0x3f6/0x11a0
       __kernel_read+0x46c/0x8c0
       integrity_kernel_read+0x89/0xd0
       ima_calc_file_hash+0x85e/0x16f0
       ima_collect_measurement+0x428/0x8d0
       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_open+0x11e/0x150
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &ei->xattr_sem --> &mm->mmap_lock --> mapping.invalidate_lock#2

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(mapping.invalidate_lock#2);
                               lock(&mm->mmap_lock);
                               lock(mapping.invalidate_lock#2);
  rlock(&ei->xattr_sem);

 *** DEADLOCK ***

3 locks held by syz.5.2044/11582:
 #0: ffff88802fd2e428 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff888026d077d8 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}, at: process_measurement+0x74b/0x1a40
 #2: ffff88801dc28580 (mapping.invalidate_lock#2){++++}-{4:4}, at: filemap_get_pages+0xc29/0x1ea0

stack backtrace:
CPU: 0 UID: 0 PID: 11582 Comm: syz.5.2044 Not tainted 6.16.0-rc4-syzkaller-00286-gc435a4f487e8-dirty #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
 down_read+0x46/0x2e0
 ext4_readpage_inline+0x36/0x6a0
 ext4_read_folio+0x16c/0x320
 filemap_read_folio+0x117/0x380
 filemap_get_pages+0xd4e/0x1ea0
 filemap_read+0x3f6/0x11a0
 __kernel_read+0x46c/0x8c0
 integrity_kernel_read+0x89/0xd0
 ima_calc_file_hash+0x85e/0x16f0
 ima_collect_measurement+0x428/0x8d0
 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_open+0x11e/0x150
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1050d8e929
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:00007f1051b5f038 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f1050fb5fa0 RCX: 00007f1050d8e929
RDX: 0000000000000040 RSI: 0000000000141242 RDI: 0000200000000140
RBP: 00007f1050e10b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f1050fb5fa0 R15: 00007ffd01b35618
 </TASK>
