======================================================
WARNING: possible circular locking dependency detected
6.1.0-rc5-next-20221114 #1 Not tainted
------------------------------------------------------
syz-executor.5/859 is trying to acquire lock:
ffff88800ffb03f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: __jbd2_log_wait_for_space+0x238/0x460

but task is already holding lock:
ffff88803e9621d0 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: vfs_unlink+0xd9/0x930

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&sb->s_type->i_mutex_key#6){++++}-{3:3}:
       down_read+0x9c/0x450
       ext4_bmap+0x52/0x470
       bmap+0xb0/0x130
       jbd2_journal_bmap+0xac/0x190
       jbd2_journal_flush+0x857/0xc10
       __ext4_ioctl+0x9b0/0x4340
       __x64_sys_ioctl+0x19e/0x210
       do_syscall_64+0x3f/0x90
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

-> #0 (&journal->j_checkpoint_mutex){+.+.}-{3:3}:
       __lock_acquire+0x2a02/0x5e70
       lock_acquire+0x1a6/0x530
       mutex_lock_io_nested+0x14c/0x1330
       __jbd2_log_wait_for_space+0x238/0x460
       add_transaction_credits+0xa42/0xb80
       start_this_handle+0x3ac/0x14c0
       jbd2__journal_start+0x394/0x8d0
       __ext4_journal_start_sb+0x395/0x470
       ext4_unlink+0x4e8/0x8c0
       vfs_unlink+0x35e/0x930
       do_unlinkat+0x398/0x620
       __x64_sys_unlink+0xca/0x110
       do_syscall_64+0x3f/0x90
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&sb->s_type->i_mutex_key#6);
                               lock(&journal->j_checkpoint_mutex);
                               lock(&sb->s_type->i_mutex_key#6);
  lock(&journal->j_checkpoint_mutex);

 *** DEADLOCK ***

3 locks held by syz-executor.5/859:
 #0: ffff88800ff2c438 (sb_writers#3){.+.+}-{0:0}, at: do_unlinkat+0x187/0x620
 #1: ffff88801c3da1d0 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: do_unlinkat+0x274/0x620
 #2: ffff88803e9621d0 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: vfs_unlink+0xd9/0x930

stack backtrace:
CPU: 1 PID: 859 Comm: syz-executor.5 Not tainted 6.1.0-rc5-next-20221114 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x8f/0xb7
 check_noncircular+0x263/0x2e0
 __lock_acquire+0x2a02/0x5e70
 lock_acquire+0x1a6/0x530
 mutex_lock_io_nested+0x14c/0x1330
 __jbd2_log_wait_for_space+0x238/0x460
 add_transaction_credits+0xa42/0xb80
 start_this_handle+0x3ac/0x14c0
 jbd2__journal_start+0x394/0x8d0
 __ext4_journal_start_sb+0x395/0x470
 ext4_unlink+0x4e8/0x8c0
 vfs_unlink+0x35e/0x930
 do_unlinkat+0x398/0x620
 __x64_sys_unlink+0xca/0x110
 do_syscall_64+0x3f/0x90
 entry_SYSCALL_64_after_hwframe+0x72/0xdc
RIP: 0033:0x7fd9942eb457
Code: 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 57 00 00 00 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:00007ffc21f61968 EFLAGS: 00000206 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd9942eb457
RDX: 00007ffc21f619a0 RSI: 00007ffc21f619a0 RDI: 00007ffc21f61a30
RBP: 00007ffc21f61a30 R08: 0000000000000001 R09: 00007ffc21f61800
R10: 0000555556404cdb R11: 0000000000000206 R12: 00007fd994345105
R13: 00007ffc21f62af0 R14: 0000555556404c20 R15: 00007ffc21f62b30
 </TASK>
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=0 sclass=netlink_audit_socket pid=86190 comm=syz-executor.7
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=0 sclass=netlink_audit_socket pid=86209 comm=syz-executor.7
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=0 sclass=netlink_audit_socket pid=86321 comm=syz-executor.7
SELinux: unrecognized netlink message: protocol=9 nlmsg_type=0 sclass=netlink_audit_socket pid=86354 comm=syz-executor.7