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

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

-> #3 (&journal->j_checkpoint_mutex){+.+.}-{3:3}:
       mutex_lock_io_nested+0x148/0x1310
       jbd2_journal_flush+0x19a/0xc00
       __ext4_ioctl+0x9e9/0x4090
       __x64_sys_ioctl+0x19a/0x210
       do_syscall_64+0x3b/0x90
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #2 (&journal->j_barrier){+.+.}-{3:3}:
       __mutex_lock+0x136/0x14d0
       jbd2_journal_lock_updates+0x15e/0x310
       ext4_change_inode_journal_flag+0x17f/0x530
       ext4_fileattr_set+0x140d/0x18a0
       vfs_fileattr_set+0x77c/0xb80
       do_vfs_ioctl+0xfc2/0x1610
       __x64_sys_ioctl+0x10c/0x210
       do_syscall_64+0x3b/0x90
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       percpu_down_write+0x4d/0x3d0
       ext4_ind_migrate+0x237/0x830
       ext4_fileattr_set+0x1434/0x18a0
       vfs_fileattr_set+0x77c/0xb80
       do_vfs_ioctl+0xfc2/0x1610
       __x64_sys_ioctl+0x10c/0x210
       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/0x4090
       __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:

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.1/4228:
 #0: ffff88800ff72170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x15e/0x310
 #1: ffff88800ff723f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc00

stack backtrace:
CPU: 0 PID: 4228 Comm: syz-executor.1 Not tainted 6.0.0-rc2-next-20220826 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 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/0x4090
 __x64_sys_ioctl+0x19a/0x210
 do_syscall_64+0x3b/0x90
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ff987058b19
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:00007ff9845ce188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff98716bf60 RCX: 00007ff987058b19
RDX: 0000000020000240 RSI: 000000004004662b RDI: 0000000000000006
RBP: 00007ff9870b2f6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffbc2cdf2f R14: 00007ff9845ce300 R15: 0000000000022000
 </TASK>
kernel write not supported for file /snd/seq (pid: 12 comm: kworker/0:1)
process 'syz-executor.7' launched '/dev/fd/-1/./file1' with NULL argv: empty string added
syz-executor.4 (4226) used greatest stack depth: 23512 bytes left
loop5: detected capacity change from 0 to 2048
loop3: detected capacity change from 0 to 40
EXT4-fs (loop5): mounted filesystem without journal. Quota mode: none.
ext4 filesystem being mounted at /syzkaller-testdir981165800/syzkaller.BVqCVb/8/file0 supports timestamps until 2038 (0x7fffffff)
loop2: detected capacity change from 0 to 8
FAT-fs (loop2): Unrecognized mount option "01777777777777777777777" or missing value
kernel write not supported for file /snd/seq (pid: 20 comm: kworker/1:0)
loop2: detected capacity change from 0 to 8
FAT-fs (loop2): Unrecognized mount option "00000000000000000000004" or missing value
sr 1:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
sr 1:0:0:0: [sr0] tag#0 Sense Key : Not Ready [current] 
sr 1:0:0:0: [sr0] tag#0 Add. Sense: Medium not present
sr 1:0:0:0: [sr0] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 40 00
I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 27 prio class 2
EXT4-fs (loop5): unmounting filesystem.
Bluetooth: hci7: HCI_REQ-0x0406
Bluetooth: hci0: HCI_REQ-0x0406
Bluetooth: hci3: HCI_REQ-0x0406
Bluetooth: hci2: HCI_REQ-0x0406
Bluetooth: hci1: HCI_REQ-0x0406