======================================================
WARNING: possible circular locking dependency detected
6.1.0-rc2-next-20221028 #1 Not tainted
------------------------------------------------------
syz-executor.3/18197 is trying to acquire lock:
ffff88800ad00400 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: ext4_bmap+0x4e/0x480

but task is already holding lock:
ffff88800f7d43f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc10

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&journal->j_checkpoint_mutex){+.+.}-{3:3}:
       mutex_lock_io_nested+0x148/0x1320
       jbd2_journal_flush+0x19a/0xc10
       __ext4_ioctl+0x9e9/0x40b0
       __x64_sys_ioctl+0x19a/0x220
       do_syscall_64+0x3b/0xa0
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

-> #2 (&journal->j_barrier){+.+.}-{3:3}:
       __mutex_lock+0x136/0x14e0
       jbd2_journal_lock_updates+0x15e/0x320
       ext4_change_inode_journal_flag+0x17f/0x540
       ext4_fileattr_set+0x1427/0x18d0
       vfs_fileattr_set+0x77c/0xb90
       do_vfs_ioctl+0xfc1/0x1620
       __x64_sys_ioctl+0x10c/0x220
       do_syscall_64+0x3b/0xa0
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

-> #1 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       percpu_down_write+0x4d/0x360
       ext4_ind_migrate+0x237/0x840
       ext4_fileattr_set+0x144e/0x18d0
       vfs_fileattr_set+0x77c/0xb90
       do_vfs_ioctl+0xfc1/0x1620
       __x64_sys_ioctl+0x10c/0x220
       do_syscall_64+0x3b/0xa0
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

-> #0 (&sb->s_type->i_mutex_key#6){++++}-{3:3}:
       __lock_acquire+0x2a02/0x5e80
       lock_acquire+0x1a2/0x540
       down_read+0x98/0x460
       ext4_bmap+0x4e/0x480
       bmap+0xac/0x130
       jbd2_journal_bmap+0xa8/0x190
       jbd2_journal_flush+0x853/0xc10
       __ext4_ioctl+0x9e9/0x40b0
       __x64_sys_ioctl+0x19a/0x220
       do_syscall_64+0x3b/0xa0
       entry_SYSCALL_64_after_hwframe+0x72/0xdc

other info that might help us debug this:

Chain exists of:
  &sb->s_type->i_mutex_key#6 --> &journal->j_barrier --> &journal->j_checkpoint_mutex

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

2 locks held by syz-executor.3/18197:
 #0: ffff88800f7d4170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x15e/0x320
 #1: ffff88800f7d43f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc10

stack backtrace:
CPU: 1 PID: 18197 Comm: syz-executor.3 Not tainted 6.1.0-rc2-next-20221028 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x8b/0xc3
 check_noncircular+0x263/0x2f0
 __lock_acquire+0x2a02/0x5e80
 lock_acquire+0x1a2/0x540
 down_read+0x98/0x460
 ext4_bmap+0x4e/0x480
 bmap+0xac/0x130
 jbd2_journal_bmap+0xa8/0x190
 jbd2_journal_flush+0x853/0xc10
 __ext4_ioctl+0x9e9/0x40b0
 __x64_sys_ioctl+0x19a/0x220
 do_syscall_64+0x3b/0xa0
 entry_SYSCALL_64_after_hwframe+0x72/0xdc
RIP: 0033:0x7f1087906b19
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:00007f1084e7c188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f1087a19f60 RCX: 00007f1087906b19
RDX: 0000000020000040 RSI: 000000004004662b RDI: 0000000000000004
RBP: 00007f1087960f6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffba38ed6f R14: 00007f1084e7c300 R15: 0000000000022000
 </TASK>
cgroup: fork rejected by pids controller in /syz4
ext3: Unknown parameter 'noacl'
ext3: Unknown parameter 'noacl'