====================================================== WARNING: possible circular locking dependency detected 5.2.0-rc1+ #1 Not tainted ------------------------------------------------------ syz-executor.5/8106 is trying to acquire lock: 0000000004fe485f (&mm->mmap_sem#2){++++}, at: do_user_addr_fault arch/x86/mm/fault.c:1408 [inline] 0000000004fe485f (&mm->mmap_sem#2){++++}, at: __do_page_fault+0x70f/0xa20 arch/x86/mm/fault.c:1523 but task is already holding lock: 0000000076931b9b (&sb->s_type->i_mutex_key#10){+.+.}, at: inode_trylock include/linux/fs.h:798 [inline] 0000000076931b9b (&sb->s_type->i_mutex_key#10){+.+.}, at: ext4_file_write_iter+0x1e9/0xe90 fs/ext4/file.c:232 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sb->s_type->i_mutex_key#10){+.+.}: down_write+0x38/0xa0 kernel/locking/rwsem.c:66 inode_lock include/linux/fs.h:778 [inline] process_measurement+0x69e/0x14b0 security/integrity/ima/ima_main.c:207 ima_file_mmap+0xf0/0x110 security/integrity/ima/ima_main.c:342 security_file_mprotect+0x91/0xc0 security/security.c:1430 do_mprotect_pkey+0x3b7/0x7f0 mm/mprotect.c:550 __do_sys_pkey_mprotect mm/mprotect.c:590 [inline] __se_sys_pkey_mprotect mm/mprotect.c:587 [inline] __x64_sys_pkey_mprotect+0x92/0xf0 mm/mprotect.c:587 do_syscall_64+0xd0/0x530 arch/x86/entry/common.c:301 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&mm->mmap_sem#2){++++}: lock_acquire+0x173/0x3d0 kernel/locking/lockdep.c:4302 down_read+0x3f/0x1e0 kernel/locking/rwsem.c:24 do_user_addr_fault arch/x86/mm/fault.c:1408 [inline] __do_page_fault+0x70f/0xa20 arch/x86/mm/fault.c:1523 do_page_fault+0x64/0x3a7 arch/x86/mm/fault.c:1554 page_fault+0x1e/0x30 arch/x86/entry/entry_64.S:1156 fault_in_pages_readable arch/x86/include/asm/smap.h:57 [inline] iov_iter_fault_in_readable+0x287/0x3a0 lib/iov_iter.c:425 generic_perform_write+0x18e/0x480 mm/filemap.c:3195 __generic_file_write_iter+0x201/0x580 mm/filemap.c:3334 ext4_file_write_iter+0x288/0xe90 fs/ext4/file.c:266 call_write_iter include/linux/fs.h:1872 [inline] new_sync_write+0x3fd/0x7e0 fs/read_write.c:483 __vfs_write+0x94/0x110 fs/read_write.c:496 vfs_write+0x150/0x4e0 fs/read_write.c:558 ksys_write+0x105/0x220 fs/read_write.c:611 __do_sys_write fs/read_write.c:623 [inline] __se_sys_write fs/read_write.c:620 [inline] __x64_sys_write+0x6e/0xb0 fs/read_write.c:620 do_syscall_64+0xd0/0x530 arch/x86/entry/common.c:301 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#10); lock(&mm->mmap_sem#2); lock(&sb->s_type->i_mutex_key#10); lock(&mm->mmap_sem#2); *** DEADLOCK *** 3 locks held by syz-executor.5/8106: #0: 0000000018649f57 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0xa7/0xd0 fs/file.c:801 #1: 00000000f13f02b5 (sb_writers#3){.+.+}, at: file_start_write include/linux/fs.h:2837 [inline] #1: 00000000f13f02b5 (sb_writers#3){.+.+}, at: vfs_write+0x321/0x4e0 fs/read_write.c:557 #2: 0000000076931b9b (&sb->s_type->i_mutex_key#10){+.+.}, at: inode_trylock include/linux/fs.h:798 [inline] #2: 0000000076931b9b (&sb->s_type->i_mutex_key#10){+.+.}, at: ext4_file_write_iter+0x1e9/0xe90 fs/ext4/file.c:232 stack backtrace: CPU: 1 PID: 8106 Comm: syz-executor.5 Not tainted 5.2.0-rc1+ #1 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x113/0x167 lib/dump_stack.c:113 print_circular_bug.cold.59+0x1bd/0x27d kernel/locking/lockdep.c:1564 check_prev_add kernel/locking/lockdep.c:2309 [inline] check_prevs_add kernel/locking/lockdep.c:2417 [inline] validate_chain kernel/locking/lockdep.c:2799 [inline] __lock_acquire+0x3853/0x55b0 kernel/locking/lockdep.c:3792 lock_acquire+0x173/0x3d0 kernel/locking/lockdep.c:4302 down_read+0x3f/0x1e0 kernel/locking/rwsem.c:24 do_user_addr_fault arch/x86/mm/fault.c:1408 [inline] __do_page_fault+0x70f/0xa20 arch/x86/mm/fault.c:1523 do_page_fault+0x64/0x3a7 arch/x86/mm/fault.c:1554 page_fault+0x1e/0x30 arch/x86/entry/entry_64.S:1156 RIP: 0010:fault_in_pages_readable include/linux/pagemap.h:601 [inline] RIP: 0010:iov_iter_fault_in_readable+0x287/0x3a0 lib/iov_iter.c:425 Code: 48 39 d7 0f 82 19 ff ff ff 0f 1f 00 0f ae e8 44 89 c0 8a 0a 0f 1f 00 85 c0 41 88 4d c0 74 da e9 f7 fe ff ff 0f 1f 00 0f ae e8 <8a> 11 0f 1f 00 85 c0 41 88 55 80 0f 85 03 ff ff ff 4c 29 e6 e9 48 RSP: 0018:ffff8880884e78b8 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 1ffff1101109cf19 RCX: 000000002000127f RDX: 00000000000000ff RSI: 0000000000001000 RDI: ffff8880884e7c01 RBP: ffff8880884e7990 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000001000 R13: ffff8880884e7968 R14: ffff8880884e7c90 R15: 0000000000000000 generic_perform_write+0x18e/0x480 mm/filemap.c:3195 __generic_file_write_iter+0x201/0x580 mm/filemap.c:3334 ext4_file_write_iter+0x288/0xe90 fs/ext4/file.c:266 call_write_iter include/linux/fs.h:1872 [inline] new_sync_write+0x3fd/0x7e0 fs/read_write.c:483 __vfs_write+0x94/0x110 fs/read_write.c:496 vfs_write+0x150/0x4e0 fs/read_write.c:558 ksys_write+0x105/0x220 fs/read_write.c:611 __do_sys_write fs/read_write.c:623 [inline] __se_sys_write fs/read_write.c:620 [inline] __x64_sys_write+0x6e/0xb0 fs/read_write.c:620 do_syscall_64+0xd0/0x530 arch/x86/entry/common.c:301 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x459279 Code: fd b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 0f 83 cb b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007feca41ebc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000459279 RDX: 000000000000ff7f RSI: 0000000020000280 RDI: 0000000000000003 RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007feca41ec6d4 R13: 00000000004c8aa4 R14: 00000000004df468 R15: 00000000ffffffff