====================================================== WARNING: possible circular locking dependency detected 6.0.0-rc3-next-20220829 #1 Not tainted ------------------------------------------------------ syz-executor.1/23052 is trying to acquire lock: ffff8880101163f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: __jbd2_log_wait_for_space+0x234/0x460 but task is already holding lock: ffff888010112530 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x1a0/0x4f0 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/0x1a70 do_page_mkwrite+0x1a0/0x4f0 __handle_mm_fault+0x12ac/0x34c0 handle_mm_fault+0x2e6/0xa20 do_user_addr_fault+0x536/0x1300 exc_page_fault+0x98/0x1a0 asm_exc_page_fault+0x22/0x30 -> #2 (&mm->mmap_lock#2){++++}-{3:3}: internal_get_user_pages_fast+0x133a/0x2ec0 get_user_pages_fast+0x66/0xa0 __iov_iter_get_pages_alloc+0x38d/0x2290 iov_iter_get_pages2+0xa4/0x100 bio_iov_iter_get_pages+0x1da/0x10b0 iomap_dio_bio_iter+0x92f/0x1510 __iomap_dio_rw+0xe14/0x1bd0 iomap_dio_rw+0x3c/0xa0 ext4_file_write_iter+0xa96/0x1820 vfs_write+0x9c3/0xd90 __x64_sys_pwrite64+0x1fb/0x260 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (&sb->s_type->i_mutex_key#6){++++}-{3:3}: down_read+0x98/0x450 ext4_bmap+0x4e/0x470 bmap+0xac/0x120 jbd2_journal_bmap+0xa8/0x180 jbd2_journal_flush+0x853/0xc00 __ext4_ioctl+0x9e9/0x4090 __x64_sys_ioctl+0x19a/0x210 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&journal->j_checkpoint_mutex){+.+.}-{3:3}: __lock_acquire+0x2a02/0x5e70 lock_acquire+0x1a2/0x530 mutex_lock_io_nested+0x148/0x1310 __jbd2_log_wait_for_space+0x234/0x460 add_transaction_credits+0xa42/0xb80 start_this_handle+0x3ac/0x14c0 jbd2__journal_start+0x390/0x8d0 __ext4_journal_start_sb+0x391/0x470 ext4_dirty_inode+0x9d/0x110 __mark_inode_dirty+0x455/0xf00 generic_update_time+0x26b/0x410 file_update_time+0x22b/0x280 ext4_page_mkwrite+0x2ea/0x1a70 do_page_mkwrite+0x1a0/0x4f0 __handle_mm_fault+0x12ac/0x34c0 handle_mm_fault+0x2e6/0xa20 do_user_addr_fault+0x536/0x1300 exc_page_fault+0x98/0x1a0 asm_exc_page_fault+0x22/0x30 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.1/23052: #0: ffff8880085ab958 (&mm->mmap_lock#2){++++}-{3:3}, at: do_user_addr_fault+0x337/0x1300 #1: ffff888010112530 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x1a0/0x4f0 stack backtrace: CPU: 0 PID: 23052 Comm: syz-executor.1 Not tainted 6.0.0-rc3-next-20220829 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Call Trace: dump_stack_lvl+0x8b/0xb3 check_noncircular+0x263/0x2e0 __lock_acquire+0x2a02/0x5e70 lock_acquire+0x1a2/0x530 mutex_lock_io_nested+0x148/0x1310 __jbd2_log_wait_for_space+0x234/0x460 add_transaction_credits+0xa42/0xb80 start_this_handle+0x3ac/0x14c0 jbd2__journal_start+0x390/0x8d0 __ext4_journal_start_sb+0x391/0x470 ext4_dirty_inode+0x9d/0x110 __mark_inode_dirty+0x455/0xf00 generic_update_time+0x26b/0x410 file_update_time+0x22b/0x280 ext4_page_mkwrite+0x2ea/0x1a70 do_page_mkwrite+0x1a0/0x4f0 __handle_mm_fault+0x12ac/0x34c0 handle_mm_fault+0x2e6/0xa20 do_user_addr_fault+0x536/0x1300 exc_page_fault+0x98/0x1a0 asm_exc_page_fault+0x22/0x30 RIP: 0033:0x7f1b50d8f673 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:00007fffbc567c98 EFLAGS: 00010287 RAX: 0000001b2d824000 RBX: 00007f1b50b69e70 RCX: 0000001b2d820000 RDX: 0000001b2d824004 RSI: 00007f1b50b88ae8 RDI: 00000000816722d2 RBP: 0000000000000d01 R08: 0000001b2e820000 R09: 0000001b2d82001c R10: 0000000000001d27 R11: 00000000805edd2b R12: 00007f1b50b6f810 R13: 00007f1b50b88ae8 R14: ffffffff8133eada R15: 00007f1b50f04ff0 loop1: detected capacity change from 0 to 40 syz-executor.1: attempt to access beyond end of device loop1: rw=2049, sector=40, nr_sectors = 4 limit=40 buffer_io_error: 438 callbacks suppressed Buffer I/O error on dev loop1, logical block 10, lost async page write loop0: detected capacity change from 0 to 40 loop1: detected capacity change from 0 to 40 syz-executor.1: attempt to access beyond end of device loop1: rw=2049, sector=40, nr_sectors = 4 limit=40 Buffer I/O error on dev loop1, logical block 10, lost async page write loop1: detected capacity change from 0 to 40 loop3: detected capacity change from 0 to 40 loop0: detected capacity change from 0 to 40 syz-executor.1: attempt to access beyond end of device loop1: rw=2049, sector=40, nr_sectors = 4 limit=40 Buffer I/O error on dev loop1, logical block 10, lost async page write syz-executor.3: attempt to access beyond end of device loop3: rw=2049, sector=40, nr_sectors = 4 limit=40 Buffer I/O error on dev loop3, logical block 10, lost async page write syz-executor.0: attempt to access beyond end of device loop0: rw=2049, sector=40, nr_sectors = 4 limit=40 Buffer I/O error on dev loop0, logical block 10, lost async page write loop1: detected capacity change from 0 to 40 loop3: detected capacity change from 0 to 40 loop0: detected capacity change from 0 to 40 syz-executor.3: attempt to access beyond end of device loop3: rw=2049, sector=40, nr_sectors = 4 limit=40 Buffer I/O error on dev loop3, logical block 10, lost async page write syz-executor.1: attempt to access beyond end of device loop1: rw=2049, sector=40, nr_sectors = 4 limit=40 Buffer I/O error on dev loop1, logical block 10, lost async page write raw_sendmsg: syz-executor.7 forgot to set AF_INET. Fix it! syz-executor.0: attempt to access beyond end of device loop0: rw=2049, sector=40, nr_sectors = 4 limit=40 Buffer I/O error on dev loop0, logical block 10, lost async page write loop3: detected capacity change from 0 to 40 syz-executor.3: attempt to access beyond end of device loop3: rw=2049, sector=40, nr_sectors = 4 limit=40 Buffer I/O error on dev loop3, logical block 10, lost async page write UDC core: USB Raw Gadget: couldn't find an available UDC or it's busy misc raw-gadget: fail, usb_gadget_register_driver returned -16 random: crng reseeded on system resumption platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 random: crng reseeded on system resumption platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 UDC core: USB Raw Gadget: couldn't find an available UDC or it's busy misc raw-gadget: fail, usb_gadget_register_driver returned -16 platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 random: crng reseeded on system resumption platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 random: crng reseeded on system resumption random: crng reseeded on system resumption random: crng reseeded on system resumption