EXT4-fs warning (device loop0): ext4_enable_quotas:6818: Failed to enable quota tracking (type=0, err=-116). Please run e2fsck to fix.
EXT4-fs (loop0): mount failed
EXT4-fs error (device loop6): ext4_quota_enable:6781: comm syz-executor.6: Bad quota inode # 3
======================================================
WARNING: possible circular locking dependency detected
6.0.0-rc3-next-20220829 #1 Not tainted
------------------------------------------------------
syz-executor.3/17267 is trying to acquire lock:
ffff88800bd78400 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: ext4_bmap+0x4e/0x470
but task is already holding lock:
ffff88800ffd83f8 (&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-fs warning (device loop6): ext4_enable_quotas:6818: Failed to enable quota tracking (type=0, err=-116). Please run e2fsck to fix.
__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
EXT4-fs (loop6): mount failed
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.3/17267:
#0: ffff88800ffd8170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x15e/0x310
#1: ffff88800ffd83f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x48b/0xc00
stack backtrace:
CPU: 1 PID: 17267 Comm: syz-executor.3 Not tainted 6.0.0-rc3-next-20220829 #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:0x7f6854005b19
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:00007f685157b188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f6854118f60 RCX: 00007f6854005b19
RDX: 0000000020000340 RSI: 000000004004662b RDI: 0000000000000004
RBP: 00007f685405ff6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffcd47a33f R14: 00007f685157b300 R15: 0000000000022000
</TASK>
loop6: detected capacity change from 0 to 512
loop0: detected capacity change from 0 to 512
loop5: detected capacity change from 0 to 512
EXT4-fs error (device loop6): ext4_quota_enable:6781: comm syz-executor.6: Bad quota inode # 3
EXT4-fs warning (device loop6): ext4_enable_quotas:6818: Failed to enable quota tracking (type=0, err=-116). Please run e2fsck to fix.
EXT4-fs (loop6): mount failed
loop7: detected capacity change from 0 to 512
EXT4-fs error (device loop7): __ext4_fill_super:5244: inode #2: comm syz-executor.7: iget: root inode unallocated
EXT4-fs (loop7): get root inode failed
EXT4-fs (loop7): mount failed
EXT4-fs error (device loop5): __ext4_fill_super:5244: inode #2: comm syz-executor.5: iget: root inode unallocated
EXT4-fs error (device loop0): ext4_ext_check_inode:497: inode #2: comm syz-executor.0: pblk 0 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
EXT4-fs (loop5): get root inode failed
EXT4-fs (loop5): mount failed
EXT4-fs (loop0): get root inode failed
EXT4-fs (loop0): mount failed
loop4: detected capacity change from 0 to 512
loop6: detected capacity change from 0 to 512
EXT4-fs error (device loop4): __ext4_fill_super:5244: inode #2: comm syz-executor.4: iget: root inode unallocated
EXT4-fs (loop4): get root inode failed
EXT4-fs (loop4): mount failed
loop7: detected capacity change from 0 to 512
EXT4-fs error (device loop6): ext4_quota_enable:6781: comm syz-executor.6: Bad quota inode # 3
EXT4-fs warning (device loop6): ext4_enable_quotas:6818: Failed to enable quota tracking (type=0, err=-116). Please run e2fsck to fix.
EXT4-fs (loop6): mount failed
EXT4-fs error (device loop7): __ext4_fill_super:5244: inode #2: comm syz-executor.7: iget: root inode unallocated
EXT4-fs (loop7): get root inode failed
EXT4-fs (loop7): mount failed