FAT-fs (loop6): bogus number of reserved sectors FAT-fs (loop6): Can't find a valid FAT filesystem warning: checkpointing journal with EXT4_IOC_CHECKPOINT_FLAG_ZEROOUT can be slow ====================================================== WARNING: possible circular locking dependency detected 6.0.0-next-20221017 #1 Not tainted ------------------------------------------------------ syz-executor.4/5105 is trying to acquire lock: ffff88800c990400 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: ext4_bmap+0x4e/0x470 but task is already holding lock: ffff88801006c3f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc00 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&journal->j_checkpoint_mutex){+.+.}-{3:3}: 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_writepages+0x11c2/0x3690 do_writepages+0x1b0/0x6a0 filemap_fdatawrite_wbc+0x147/0x1b0 __filemap_fdatawrite_range+0xb6/0x100 file_write_and_wait_range+0xb6/0x130 ext4_sync_file+0x21d/0xfa0 vfs_fsync_range+0x13d/0x230 ext4_buffered_write_iter+0x37d/0x460 ext4_file_write_iter+0x3fb/0x1900 do_iter_readv_writev+0x211/0x3c0 do_iter_write+0x18b/0x700 vfs_iter_write+0x70/0xa0 iter_file_splice_write+0x73a/0xca0 direct_splice_actor+0x10f/0x170 splice_direct_to_actor+0x336/0x8c0 do_splice_direct+0x1b8/0x290 do_sendfile+0xb1d/0x1280 __x64_sys_sendfile64+0x1d1/0x210 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (&sbi->s_writepages_rwsem){++++}-{0:0}: percpu_down_write+0x4d/0x350 ext4_ind_migrate+0x237/0x830 ext4_fileattr_set+0x144e/0x18c0 vfs_fileattr_set+0x77c/0xb80 do_vfs_ioctl+0xfc1/0x1610 __x64_sys_ioctl+0x10c/0x210 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&sb->s_type->i_mutex_key#6){++++}-{3:3}: __lock_acquire+0x2a02/0x5e70 lock_acquire+0x1a2/0x530 down_read+0x98/0x450 ext4_bmap+0x4e/0x470 bmap+0xac/0x120 jbd2_journal_bmap+0xa8/0x180 jbd2_journal_flush+0x853/0xc00 __ext4_ioctl+0x9e9/0x40a0 __x64_sys_ioctl+0x19a/0x210 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Chain exists of: &sb->s_type->i_mutex_key#6 --> &sbi->s_writepages_rwsem --> &journal->j_checkpoint_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&journal->j_checkpoint_mutex); lock(&sbi->s_writepages_rwsem); lock(&journal->j_checkpoint_mutex); lock(&sb->s_type->i_mutex_key#6); *** DEADLOCK *** 2 locks held by syz-executor.4/5105: #0: ffff88801006c170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x15e/0x310 #1: ffff88801006c3f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc00 stack backtrace: CPU: 0 PID: 5105 Comm: syz-executor.4 Not tainted 6.0.0-next-20221017 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Call Trace: dump_stack_lvl+0x8b/0xb3 check_noncircular+0x263/0x2e0 __lock_acquire+0x2a02/0x5e70 lock_acquire+0x1a2/0x530 down_read+0x98/0x450 ext4_bmap+0x4e/0x470 bmap+0xac/0x120 jbd2_journal_bmap+0xa8/0x180 jbd2_journal_flush+0x853/0xc00 __ext4_ioctl+0x9e9/0x40a0 __x64_sys_ioctl+0x19a/0x210 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fe3c8161b19 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 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fe3c56d7188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fe3c8274f60 RCX: 00007fe3c8161b19 RDX: 0000000020000100 RSI: 000000004004662b RDI: 0000000000000004 RBP: 00007fe3c81bbf6d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe32f99aaf R14: 00007fe3c56d7300 R15: 0000000000022000