====================================================== WARNING: possible circular locking dependency detected 6.1.0-rc2-next-20221028 #1 Not tainted ------------------------------------------------------ syz-executor.4/84055 is trying to acquire lock: ffff88800f82c3f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: __jbd2_log_wait_for_space+0x234/0x470 but task is already holding lock: ffff88800f828530 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x1a0/0x650 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (sb_pagefaults){.+.+}-{0:0}: ext4_page_mkwrite+0x1f8/0x1a80 do_page_mkwrite+0x1a0/0x650 __handle_mm_fault+0x12ac/0x3650 handle_mm_fault+0x27f/0x970 do_user_addr_fault+0x536/0x1310 exc_page_fault+0x98/0x1b0 asm_exc_machine_check-0xe/0x40 -> #2 (&mm->mmap_lock#2){++++}-{3:3}: down_read+0x98/0x460 do_user_addr_fault+0xb00/0x1310 exc_page_fault+0x98/0x1b0 asm_exc_machine_check-0xe/0x40 fault_in_readable+0x143/0x260 fault_in_iov_iter_readable+0x252/0x2d0 generic_perform_write+0x1b0/0x590 ext4_buffered_write_iter+0x164/0x470 ext4_file_write_iter+0x3fb/0x1910 vfs_write+0x9c3/0xda0 ksys_write+0x127/0x260 do_syscall_64+0x3b/0xa0 entry_SYSCALL_64_after_hwframe+0x72/0xdc -> #1 (&sb->s_type->i_mutex_key#6){++++}-{3:3}: down_read+0x98/0x460 ext4_bmap+0x4e/0x480 bmap+0xac/0x130 jbd2_journal_bmap+0xa8/0x190 jbd2_journal_flush+0x853/0xc10 __ext4_ioctl+0x9e9/0x40b0 __x64_sys_ioctl+0x19a/0x220 do_syscall_64+0x3b/0xa0 entry_SYSCALL_64_after_hwframe+0x72/0xdc -> #0 (&journal->j_checkpoint_mutex){+.+.}-{3:3}: __lock_acquire+0x2a02/0x5e80 lock_acquire+0x1a2/0x540 mutex_lock_io_nested+0x148/0x1320 __jbd2_log_wait_for_space+0x234/0x470 add_transaction_credits+0xa42/0xb90 start_this_handle+0x3ac/0x14d0 jbd2__journal_start+0x390/0x8e0 __ext4_journal_start_sb+0x391/0x480 ext4_dirty_inode+0x9d/0x120 __mark_inode_dirty+0x1a6/0xe70 generic_update_time+0x217/0x2c0 file_update_time+0x22b/0x290 ext4_page_mkwrite+0x2ea/0x1a80 do_page_mkwrite+0x1a0/0x650 __handle_mm_fault+0x12ac/0x3650 handle_mm_fault+0x27f/0x970 do_user_addr_fault+0x536/0x1310 exc_page_fault+0x98/0x1b0 asm_exc_machine_check-0xe/0x40 other info that might help us debug this: Chain exists of: &journal->j_checkpoint_mutex --> &mm->mmap_lock#2 --> sb_pagefaults Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_pagefaults); lock(&mm->mmap_lock#2); lock(sb_pagefaults); lock(&journal->j_checkpoint_mutex); *** DEADLOCK *** 2 locks held by syz-executor.4/84055: #0: ffff88803fa15658 (&mm->mmap_lock#2){++++}-{3:3}, at: do_user_addr_fault+0x337/0x1310 #1: ffff88800f828530 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x1a0/0x650 stack backtrace: CPU: 0 PID: 84055 Comm: syz-executor.4 Not tainted 6.1.0-rc2-next-20221028 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Call Trace: dump_stack_lvl+0x8b/0xc3 check_noncircular+0x263/0x2f0 __lock_acquire+0x2a02/0x5e80 lock_acquire+0x1a2/0x540 mutex_lock_io_nested+0x148/0x1320 __jbd2_log_wait_for_space+0x234/0x470 add_transaction_credits+0xa42/0xb90 start_this_handle+0x3ac/0x14d0 jbd2__journal_start+0x390/0x8e0 __ext4_journal_start_sb+0x391/0x480 ext4_dirty_inode+0x9d/0x120 __mark_inode_dirty+0x1a6/0xe70 generic_update_time+0x217/0x2c0 file_update_time+0x22b/0x290 ext4_page_mkwrite+0x2ea/0x1a80 do_page_mkwrite+0x1a0/0x650 __handle_mm_fault+0x12ac/0x3650 handle_mm_fault+0x27f/0x970 do_user_addr_fault+0x536/0x1310 exc_page_fault+0x98/0x1b0 asm_exc_machine_check-0xe/0x40 RIP: 0033:0x7faeefda0673 Code: 5d c3 0f 1f 44 00 00 48 8b 0d 59 ed 0a 01 48 8b 05 4a ed 0a 01 4c 8d 81 00 00 00 01 48 39 c8 72 13 4c 39 c0 73 0e 48 8d 50 04 <89> 38 48 89 15 2c ed 0a 01 c3 52 48 8d 35 77 b7 0b 00 48 89 c2 48 RSP: 002b:00007fff1cdf2128 EFLAGS: 00010287 RAX: 0000001b2e83a000 RBX: 00007faeefb7a008 RCX: 0000001b2e820000 RDX: 0000001b2e83a004 RSI: ffffffff8371cb86 RDI: 00000000930f8cc3 RBP: 0000000000000001 R08: 0000001b2f820000 R09: 0000001b2e8399bc R10: 0000000000000cc6 R11: 00000000930f8cc7 R12: 0000000000000ddb R13: 00007faeeff0a000 R14: ffffffff8371cb86 R15: 00007faeeff15ff0 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 SELinux: security_context_str_to_sid (sysadm_u) failed with errno=-22 tmpfs: Bad value for 'mpol' netlink: 4612 bytes leftover after parsing attributes in process `syz-executor.4'. tmpfs: Bad value for 'mpol' netlink: 4612 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 4612 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 4612 bytes leftover after parsing attributes in process `syz-executor.4'. Bluetooth: hci0: command 0x0406 tx timeout