======================================================
WARNING: possible circular locking dependency detected
6.0.0-next-20221017 #1 Not tainted
------------------------------------------------------
syz-executor.2/31644 is trying to acquire lock:
ffff88800c958400 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: ext4_bmap+0x4e/0x470

but task is already holding lock:
ffff8880100203f8 (&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:

-> #1 (&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_unlink+0x4e4/0x8b0
       vfs_unlink+0x35a/0x930
       do_unlinkat+0x3a9/0x630
       __x64_sys_unlink+0xc6/0x110
       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:

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

2 locks held by syz-executor.2/31644:
 #0: ffff888010020170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x15e/0x310
 #1: ffff8880100203f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc00

stack backtrace:
CPU: 0 PID: 31644 Comm: syz-executor.2 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:
 <TASK>
 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:0x7ff1a9226b19
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:00007ff1a679c188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff1a9339f60 RCX: 00007ff1a9226b19
RDX: 0000000020000000 RSI: 000000004004662b RDI: 0000000000000003
RBP: 00007ff1a9280f6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe580a603f R14: 00007ff1a679c300 R15: 0000000000022000
 </TASK>
Bluetooth: hci7: command 0x0409 tx timeout
Bluetooth: hci7: command 0x0409 tx timeout
Bluetooth: hci7: command 0x0409 tx timeout
Bluetooth: hci7: command 0x0409 tx timeout
cgroup: fork rejected by pids controller in /syz5
Bluetooth: hci7: command 0x0409 tx timeout