====================================================== WARNING: possible circular locking dependency detected 6.0.0-syzkaller-05118-g833477fce7a1 #0 Not tainted ------------------------------------------------------ syz-executor.3/5958 is trying to acquire lock: ffff88805187e850 (&sb->s_type->i_mutex_key#8/4){+.+.}-{3:3}, at: swap_inode_boot_loader fs/ext4/ioctl.c:385 [inline] ffff88805187e850 (&sb->s_type->i_mutex_key#8/4){+.+.}-{3:3}, at: __ext4_ioctl fs/ext4/ioctl.c:1416 [inline] ffff88805187e850 (&sb->s_type->i_mutex_key#8/4){+.+.}-{3:3}, at: ext4_ioctl+0x23b4/0x5410 fs/ext4/ioctl.c:1606 but task is already holding lock: ffff88805187a218 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline] ffff88805187a218 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: lock_two_nondirectories+0xdd/0x130 fs/inode.c:1122 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&sb->s_type->i_mutex_key#8){++++}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5666 down_read+0x39/0x50 kernel/locking/rwsem.c:1499 inode_lock_shared include/linux/fs.h:766 [inline] ext4_bmap+0x55/0x410 fs/ext4/inode.c:3157 bmap+0xa1/0xd0 fs/inode.c:1799 jbd2_journal_bmap fs/jbd2/journal.c:971 [inline] __jbd2_journal_erase fs/jbd2/journal.c:1784 [inline] jbd2_journal_flush+0x5d0/0xca0 fs/jbd2/journal.c:2490 ext4_ioctl_checkpoint fs/ext4/ioctl.c:1082 [inline] __ext4_ioctl fs/ext4/ioctl.c:1586 [inline] ext4_ioctl+0x31ad/0x5410 fs/ext4/ioctl.c:1606 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (&journal->j_checkpoint_mutex){+.+.}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5666 __mutex_lock_common+0x1bd/0x26e0 kernel/locking/mutex.c:603 mutex_lock_io_nested+0x43/0x60 kernel/locking/mutex.c:833 __jbd2_log_wait_for_space+0x21d/0x6f0 fs/jbd2/checkpoint.c:110 add_transaction_credits+0x916/0xbd0 fs/jbd2/transaction.c:298 start_this_handle+0x744/0x1670 fs/jbd2/transaction.c:422 jbd2__journal_start+0x2ca/0x5b0 fs/jbd2/transaction.c:520 __ext4_journal_start_sb+0x111/0x1d0 fs/ext4/ext4_jbd2.c:105 __ext4_new_inode+0x137a/0x46f0 fs/ext4/ialloc.c:1080 ext4_whiteout_for_rename+0x24a/0x480 fs/ext4/namei.c:3721 ext4_rename fs/ext4/namei.c:3834 [inline] ext4_rename2+0x1ad7/0x4760 fs/ext4/namei.c:4164 vfs_rename+0xd53/0x1130 fs/namei.c:4756 ovl_do_rename fs/overlayfs/overlayfs.h:297 [inline] ovl_check_rename_whiteout+0x3a0/0x620 fs/overlayfs/super.c:1297 ovl_make_workdir+0x2a8/0xce0 fs/overlayfs/super.c:1417 ovl_get_workdir+0x2e4/0x410 fs/overlayfs/super.c:1532 ovl_fill_super+0x19d7/0x2790 fs/overlayfs/super.c:2088 mount_nodev+0x52/0xe0 fs/super.c:1446 legacy_get_tree+0xea/0x180 fs/fs_context.c:610 vfs_get_tree+0x88/0x270 fs/super.c:1530 do_new_mount+0x289/0xad0 fs/namespace.c:3040 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&sb->s_type->i_mutex_key#8/4){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain+0x18c1/0x6bd0 kernel/locking/lockdep.c:3829 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5053 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5666 down_write_nested+0x9e/0x180 kernel/locking/rwsem.c:1662 swap_inode_boot_loader fs/ext4/ioctl.c:385 [inline] __ext4_ioctl fs/ext4/ioctl.c:1416 [inline] ext4_ioctl+0x23b4/0x5410 fs/ext4/ioctl.c:1606 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Chain exists of: &sb->s_type->i_mutex_key#8/4 --> &journal->j_checkpoint_mutex --> &sb->s_type->i_mutex_key#8 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#8); lock(&journal->j_checkpoint_mutex); lock(&sb->s_type->i_mutex_key#8); lock(&sb->s_type->i_mutex_key#8/4); *** DEADLOCK *** 2 locks held by syz-executor.3/5958: #0: ffff88814b8b8460 (sb_writers#3){.+.+}-{0:0}, at: mnt_want_write_file+0x5a/0x1f0 fs/namespace.c:437 #1: ffff88805187a218 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline] #1: ffff88805187a218 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: lock_two_nondirectories+0xdd/0x130 fs/inode.c:1122 stack backtrace: CPU: 0 PID: 5958 Comm: syz-executor.3 Not tainted 6.0.0-syzkaller-05118-g833477fce7a1 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 check_noncircular+0x2cc/0x390 kernel/locking/lockdep.c:2175 check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain+0x18c1/0x6bd0 kernel/locking/lockdep.c:3829 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5053 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5666 down_write_nested+0x9e/0x180 kernel/locking/rwsem.c:1662 swap_inode_boot_loader fs/ext4/ioctl.c:385 [inline] __ext4_ioctl fs/ext4/ioctl.c:1416 [inline] ext4_ioctl+0x23b4/0x5410 fs/ext4/ioctl.c:1606 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fadf8e8a5a9 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fadfa025168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fadf8fabf80 RCX: 00007fadf8e8a5a9 RDX: 0000000000000000 RSI: 0000000000006611 RDI: 0000000000000003 RBP: 00007fadf8ee5580 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff6551722f R14: 00007fadfa025300 R15: 0000000000022000