warning: checkpointing journal with EXT4_IOC_CHECKPOINT_FLAG_ZEROOUT can be slow ====================================================== WARNING: possible circular locking dependency detected 6.1.0-rc2-next-20221028 #1 Not tainted ------------------------------------------------------ syz-executor.1/34690 is trying to acquire lock: ffff888008150400 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: ext4_bmap+0x4e/0x480 but task is already holding lock: ffff88800f7623f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc10 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&journal->j_checkpoint_mutex){+.+.}-{3:3}: mutex_lock_io_nested+0x148/0x1320 jbd2_journal_flush+0x19a/0xc10 __ext4_ioctl+0x9e9/0x40b0 __x64_sys_ioctl+0x19a/0x220 do_syscall_64+0x3b/0xa0 entry_SYSCALL_64_after_hwframe+0x72/0xdc -> #2 (&journal->j_barrier){+.+.}-{3:3}: __mutex_lock+0x136/0x14e0 jbd2_journal_lock_updates+0x15e/0x320 ext4_change_inode_journal_flag+0x17f/0x540 ext4_fileattr_set+0x1427/0x18d0 vfs_fileattr_set+0x77c/0xb90 do_vfs_ioctl+0xfc1/0x1620 __x64_sys_ioctl+0x10c/0x220 do_syscall_64+0x3b/0xa0 entry_SYSCALL_64_after_hwframe+0x72/0xdc -> #1 (&sbi->s_writepages_rwsem){++++}-{0:0}: percpu_down_write+0x4d/0x360 ext4_ind_migrate+0x237/0x840 ext4_fileattr_set+0x144e/0x18d0 vfs_fileattr_set+0x77c/0xb90 do_vfs_ioctl+0xfc1/0x1620 __x64_sys_ioctl+0x10c/0x220 do_syscall_64+0x3b/0xa0 entry_SYSCALL_64_after_hwframe+0x72/0xdc -> #0 (&sb->s_type->i_mutex_key#6){++++}-{3:3}: __lock_acquire+0x2a02/0x5e80 lock_acquire+0x1a2/0x540 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 other info that might help us debug this: Chain exists of: &sb->s_type->i_mutex_key#6 --> &journal->j_barrier --> &journal->j_checkpoint_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&journal->j_checkpoint_mutex); lock(&journal->j_barrier); lock(&journal->j_checkpoint_mutex); lock(&sb->s_type->i_mutex_key#6); *** DEADLOCK *** 2 locks held by syz-executor.1/34690: #0: ffff88800f762170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x15e/0x320 #1: ffff88800f7623f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc10 stack backtrace: CPU: 1 PID: 34690 Comm: syz-executor.1 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 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 RIP: 0033:0x7f683fbedb19 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:00007f683d163188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f683fd00f60 RCX: 00007f683fbedb19 RDX: 0000000020000100 RSI: 000000004004662b RDI: 0000000000000004 RBP: 00007f683fc47f6d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffeb9b1c17f R14: 00007f683d163300 R15: 0000000000022000 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2432761888 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597257248 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597322784 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597322784 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597388320 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597519392 vs 32 syz-executor.4: epoll_ctl support in io_uring is deprecated and will be removed in a future Linux kernel version. loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597584928 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597584928 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597650464 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597650464 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597716000 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597781536 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597781536 vs 32 loop5: detected capacity change from 0 to 2048 9pnet_fd: Insufficient options for proto=fd EXT4-fs (loop5): inodes count not valid: 2597847072 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597847072 vs 32 9pnet_fd: Insufficient options for proto=fd loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597912608 vs 32 9pnet_fd: Insufficient options for proto=fd loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597978144 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2597978144 vs 32 loop5: detected capacity change from 0 to 2048 9pnet_fd: Insufficient options for proto=fd EXT4-fs (loop5): inodes count not valid: 2598043680 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598043680 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598109216 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598240288 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598240288 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598305824 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598305824 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598371360 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598436896 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598436896 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598502432 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598567968 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598633504 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598633504 vs 32 I/O error, dev loop5, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Buffer I/O error on dev loop5, logical block 1, async page read loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598699040 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598764576 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598830112 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598895648 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2598961184 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599026720 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599092256 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599092256 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599157792 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599223328 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599288864 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599354400 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599485472 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599616544 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599616544 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599682080 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599747616 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599944224 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2599944224 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2600009760 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2600075296 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2600075296 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2634285088 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 2988572704 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 3221422112 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 3221422112 vs 32 loop5: detected capacity change from 0 to 2048 EXT4-fs (loop5): inodes count not valid: 3305373728 vs 32