======================================================
WARNING: possible circular locking dependency detected
6.1.0-rc1-next-20221019 #1 Not tainted
------------------------------------------------------
syz-executor.5/21683 is trying to acquire lock:
ffff88800bcd8400 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: ext4_bmap+0x4e/0x480
but task is already holding lock:
ffff8880103783f8 (&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.5/21683:
#0: ffff888010378170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x15e/0x320
#1: ffff8880103783f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc10
stack backtrace:
CPU: 1 PID: 21683 Comm: syz-executor.5 Not tainted 6.1.0-rc1-next-20221019 #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:0x7f580a922b19
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:00007f5807e98188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f580aa35f60 RCX: 00007f580a922b19
RDX: 0000000020000040 RSI: 000000004004662b RDI: 0000000000000004
RBP: 00007f580a97cf6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc66df659f R14: 00007f5807e98300 R15: 0000000000022000
</TASK>
audit: type=1326 audit(2000000060.136:32): auid=0 uid=0 gid=0 ses=4 subj=system_u:system_r:kernel_t:s0 pid=21815 comm="syz-executor.2" exe="/syz-executor.2" sig=31 arch=c000003e syscall=202 compat=0 ip=0x7f0931f85b19 code=0x0
cgroup: Need name or subsystem set
cgroup: Need name or subsystem set
cgroup: Need name or subsystem set
cgroup: Need name or subsystem set
loop0: detected capacity change from 0 to 40
syz-executor.0: attempt to access beyond end of device
loop0: rw=2049, sector=40, nr_sectors = 4 limit=40
buffer_io_error: 46 callbacks suppressed
Buffer I/O error on dev loop0, logical block 10, lost async page write
loop0: detected capacity change from 0 to 40
syz-executor.0: attempt to access beyond end of device
loop0: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop0, logical block 10, lost async page write
loop0: detected capacity change from 0 to 40
syz-executor.0: attempt to access beyond end of device
loop0: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop0, logical block 10, lost async page write
loop0: detected capacity change from 0 to 40
syz-executor.0: attempt to access beyond end of device
loop0: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop0, logical block 10, lost async page write
netlink: 8 bytes leftover after parsing attributes in process `syz-executor.0'.
netlink: 'syz-executor.0': attribute type 1 has an invalid length.
EXT4-fs (sda): re-mounted. Quota mode: none.
EXT4-fs (sda): re-mounted. Quota mode: none.
audit: type=1107 audit(2000000067.318:33): pid=23160 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 msg='�'
EXT4-fs (sda): re-mounted. Quota mode: none.
EXT4-fs (sda): re-mounted. Quota mode: none.
EXT4-fs (sda): re-mounted. Quota mode: none.