netlink: 24 bytes leftover after parsing attributes in process `syz-executor.7'.
======================================================
WARNING: possible circular locking dependency detected
6.2.0-rc6-next-20230203 #1 Not tainted
------------------------------------------------------
systemd-journal/86 is trying to acquire lock:
ffff88800ff423f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: __jbd2_log_wait_for_space+0x238/0x4b0

but task is already holding lock:
ffff888042028f90 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_setattr+0xb72/0x2490

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (mapping.invalidate_lock){++++}-{3:3}:
       down_write+0x92/0x1f0
       ext4_setattr+0xb72/0x2490
       notify_change+0xb90/0x11d0
       do_truncate+0x143/0x200
       do_sys_ftruncate+0x543/0x770
       do_syscall_64+0x3f/0x90
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

-> #1 (&sb->s_type->i_mutex_key#6){++++}-{3:3}:
       down_read+0x3d/0x50
       ext4_bmap+0x52/0x470
       bmap+0xb0/0x130
       jbd2_journal_bmap+0xac/0x1d0
       jbd2_journal_flush+0x87f/0xc90
       __ext4_ioctl+0x9fd/0x4330
       __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+0x2da7/0x63b0
       lock_acquire.part.0+0xec/0x320
       mutex_lock_io_nested+0x149/0x1300
       __jbd2_log_wait_for_space+0x238/0x4b0
       add_transaction_credits+0xa42/0xb80
       start_this_handle+0x3a6/0x14d0
       jbd2__journal_start+0x394/0x6b0
       __ext4_journal_start_sb+0x4c2/0x6f0
       ext4_truncate+0x68b/0x1410
       ext4_setattr+0x19e7/0x2490
       notify_change+0xb90/0x11d0
       do_truncate+0x143/0x200
       do_sys_ftruncate+0x543/0x770
       do_syscall_64+0x3f/0x90
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

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/86:
 #0: ffff88800ff36438 (sb_writers#3){.+.+}-{0:0}, at: do_syscall_64+0x3f/0x90
 #1: ffff888042028df0 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: do_truncate+0x131/0x200
 #2: ffff888042028f90 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_setattr+0xb72/0x2490

stack backtrace:
CPU: 1 PID: 86 Comm: systemd-journal Not tainted 6.2.0-rc6-next-20230203 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x91/0xf0
 check_noncircular+0x263/0x2e0
 __lock_acquire+0x2da7/0x63b0
 lock_acquire.part.0+0xec/0x320
 mutex_lock_io_nested+0x149/0x1300
 __jbd2_log_wait_for_space+0x238/0x4b0
 add_transaction_credits+0xa42/0xb80
 start_this_handle+0x3a6/0x14d0
 jbd2__journal_start+0x394/0x6b0
 __ext4_journal_start_sb+0x4c2/0x6f0
 ext4_truncate+0x68b/0x1410
 ext4_setattr+0x19e7/0x2490
 notify_change+0xb90/0x11d0
 do_truncate+0x143/0x200
 do_sys_ftruncate+0x543/0x770
 do_syscall_64+0x3f/0x90
 entry_SYSCALL_64_after_hwframe+0x72/0xdc
RIP: 0033:0x7f6960a09247
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:00007ffcb5a205a8 EFLAGS: 00000206 ORIG_RAX: 000000000000004d
RAX: ffffffffffffffda RBX: 00007ffcb5a205f0 RCX: 00007f6960a09247
RDX: 000055e2b5ae0ab0 RSI: 0000000000800000 RDI: 0000000000000017
RBP: 000055e2b5aebc40 R08: 0000000000000001 R09: 00000000098b3630
R10: 0000000000000010 R11: 0000000000000206 R12: 00007ffcb5a205e8
R13: 000055e2b5adc360 R14: 0000000000000703 R15: 0000000000000000
 </TASK>
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'.
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.