======================================================
WARNING: possible circular locking dependency detected
6.0.0-next-20221017 #1 Not tainted
------------------------------------------------------
systemd-journal/111 is trying to acquire lock:
ffff8880100543f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: __jbd2_log_wait_for_space+0x234/0x460

but task is already holding lock:
ffff888017ecad60 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_setattr+0x9ad/0x2940

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (mapping.invalidate_lock){++++}-{3:3}:
       down_write+0x90/0x220
       ext4_setattr+0x9ad/0x2940
       notify_change+0xcce/0x1420
       do_truncate+0x13c/0x200
       do_sys_ftruncate+0x553/0x750
       do_syscall_64+0x3b/0x90
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (&sb->s_type->i_mutex_key#6){++++}-{3:3}:
       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

-> #0 (&journal->j_checkpoint_mutex){+.+.}-{3:3}:
       __lock_acquire+0x2a02/0x5e70
       lock_acquire+0x1a2/0x530
       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_truncate+0x65a/0x1330
       ext4_setattr+0x1cf1/0x2940
       notify_change+0xcce/0x1420
       do_truncate+0x13c/0x200
       do_sys_ftruncate+0x553/0x750
       do_syscall_64+0x3b/0x90
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info that might help us debug this:

Chain exists of:
  &journal->j_checkpoint_mutex --> &sb->s_type->i_mutex_key#6 --> mapping.invalidate_lock

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

3 locks held by systemd-journal/111:
 #0: ffff888010050438 (sb_writers#3){.+.+}-{0:0}, at: do_syscall_64+0x3b/0x90
 #1: ffff888017ecabc0 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: do_truncate+0x12a/0x200
 #2: ffff888017ecad60 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_setattr+0x9ad/0x2940

stack backtrace:
CPU: 1 PID: 111 Comm: systemd-journal 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
 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_truncate+0x65a/0x1330
 ext4_setattr+0x1cf1/0x2940
 notify_change+0xcce/0x1420
 do_truncate+0x13c/0x200
 do_sys_ftruncate+0x553/0x750
 do_syscall_64+0x3b/0x90
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f9b79292247
Code: 77 01 c3 48 8b 15 49 6c 0c 00 f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 b8 4d 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 19 6c 0c 00 f7 d8 64 89 02 b8
RSP: 002b:00007ffcdcc49228 EFLAGS: 00000202 ORIG_RAX: 000000000000004d
RAX: ffffffffffffffda RBX: 00007ffcdcc49270 RCX: 00007f9b79292247
RDX: 0000558979be03e0 RSI: 0000000000800000 RDI: 0000000000000016
RBP: 0000558979be05f0 R08: 0000000000000001 R09: 0000558979be0674
R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffcdcc49268
R13: 0000558979bdc360 R14: 0000000000000703 R15: 0000000000000000
 </TASK>