Hello,
syzbot found the following issue on:
HEAD commit: 42616e0f09fb Linux 6.1.15
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=160d7fbcc80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=650737f7e9682672
dashboard link:
https://syzkaller.appspot.com/bug?extid=2519f87e4f1b003aaba2
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/f10713d1fd0f/disk-42616e0f.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/5a1307bb774e/vmlinux-42616e0f.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/388238a30fe4/Image-42616e0f.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+2519f8...@syzkaller.appspotmail.com
EXT4-fs (loop4): mounted filesystem without journal. Quota mode: writeback.
======================================================
WARNING: possible circular locking dependency detected
6.1.15-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.4/13272 is trying to acquire lock:
ffff0001029eece8 (&dquot->dq_lock){+.+.}-{3:3}, at: dquot_commit+0x54/0x240 fs/quota/dquot.c:479
but task is already holding lock:
ffff0000dcd85cd0 (&ei->i_data_sem/2){++++}-{3:3}, at: ext4_map_blocks+0x794/0x1884 fs/ext4/inode.c:644
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (&ei->i_data_sem/2){++++}-{3:3}:
down_read+0x5c/0x78 kernel/locking/rwsem.c:1509
ext4_map_blocks+0x2ac/0x1884 fs/ext4/inode.c:574
ext4_getblk+0x198/0x6ec fs/ext4/inode.c:864
ext4_bread+0x3c/0x1b0 fs/ext4/inode.c:920
ext4_quota_read+0x178/0x294 fs/ext4/super.c:7060
read_blk fs/quota/quota_tree.c:55 [inline]
find_tree_dqentry+0x164/0xa08 fs/quota/quota_tree.c:624
find_tree_dqentry+0x394/0xa08 fs/quota/quota_tree.c:640
find_tree_dqentry+0x394/0xa08 fs/quota/quota_tree.c:640
find_tree_dqentry+0x394/0xa08 fs/quota/quota_tree.c:640
find_dqentry fs/quota/quota_tree.c:652 [inline]
qtree_read_dquot+0x12c/0x634 fs/quota/quota_tree.c:672
v2_read_dquot+0xc0/0x11c fs/quota/quota_v2.c:333
dquot_acquire+0x130/0x5c4 fs/quota/dquot.c:435
ext4_acquire_dquot+0x270/0x398 fs/ext4/super.c:6740
dqget+0x844/0xc48 fs/quota/dquot.c:914
__dquot_initialize+0x344/0xb54 fs/quota/dquot.c:1492
dquot_initialize+0x24/0x34 fs/quota/dquot.c:1550
ext4_process_orphan+0x5c/0x2b8 fs/ext4/orphan.c:329
ext4_orphan_cleanup+0x99c/0x10e0 fs/ext4/orphan.c:474
__ext4_fill_super fs/ext4/super.c:5517 [inline]
ext4_fill_super+0x6e68/0x74c8 fs/ext4/super.c:5645
get_tree_bdev+0x360/0x54c fs/super.c:1324
ext4_get_tree+0x28/0x38 fs/ext4/super.c:5675
vfs_get_tree+0x90/0x274 fs/super.c:1531
do_new_mount+0x25c/0x8c8 fs/namespace.c:3040
path_mount+0x590/0xe58 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3568
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
-> #1 (&s->s_dquot.dqio_sem){++++}-{3:3}:
down_read+0x5c/0x78 kernel/locking/rwsem.c:1509
v2_read_dquot+0x50/0x11c fs/quota/quota_v2.c:332
dquot_acquire+0x130/0x5c4 fs/quota/dquot.c:435
ext4_acquire_dquot+0x270/0x398 fs/ext4/super.c:6740
dqget+0x844/0xc48 fs/quota/dquot.c:914
__dquot_initialize+0x344/0xb54 fs/quota/dquot.c:1492
dquot_initialize+0x24/0x34 fs/quota/dquot.c:1550
ext4_xattr_set+0xe8/0x350 fs/ext4/xattr.c:2475
ext4_xattr_trusted_set+0x4c/0x64 fs/ext4/xattr_trusted.c:38
__vfs_setxattr+0x388/0x3a4 fs/xattr.c:182
__vfs_setxattr_noperm+0x110/0x528 fs/xattr.c:216
__vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:277
vfs_setxattr+0x1a8/0x344 fs/xattr.c:309
do_setxattr fs/xattr.c:594 [inline]
setxattr+0x230/0x294 fs/xattr.c:617
path_setxattr+0x17c/0x258 fs/xattr.c:636
__do_sys_setxattr fs/xattr.c:652 [inline]
__se_sys_setxattr fs/xattr.c:648 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:648
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
-> #0 (&dquot->dq_lock){+.+.}-{3:3}:
check_prev_add kernel/locking/lockdep.c:3097 [inline]
check_prevs_add kernel/locking/lockdep.c:3216 [inline]
validate_chain kernel/locking/lockdep.c:3831 [inline]
__lock_acquire+0x3338/0x764c kernel/locking/lockdep.c:5055
lock_acquire+0x2f8/0x8dc kernel/locking/lockdep.c:5668
__mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
dquot_commit+0x54/0x240 fs/quota/dquot.c:479
ext4_write_dquot+0x1b0/0x284 fs/ext4/super.c:6724
ext4_mark_dquot_dirty+0xe8/0x140 fs/ext4/super.c:6772
mark_dquot_dirty fs/quota/dquot.c:346 [inline]
mark_all_dquot_dirty fs/quota/dquot.c:384 [inline]
__dquot_alloc_space+0x47c/0xd00 fs/quota/dquot.c:1722
dquot_alloc_space_nodirty include/linux/quotaops.h:300 [inline]
dquot_alloc_space include/linux/quotaops.h:313 [inline]
dquot_alloc_block include/linux/quotaops.h:337 [inline]
ext4_mb_new_blocks+0x1020/0x49c8 fs/ext4/mballoc.c:5573
ext4_ext_map_blocks+0x1740/0x688c fs/ext4/extents.c:4287
ext4_map_blocks+0x828/0x1884 fs/ext4/inode.c:651
ext4_getblk+0x198/0x6ec fs/ext4/inode.c:864
ext4_bread+0x3c/0x1b0 fs/ext4/inode.c:920
ext4_append+0x260/0x4cc fs/ext4/namei.c:83
ext4_init_new_dir+0x294/0x8e4 fs/ext4/namei.c:2956
ext4_mkdir+0x3d4/0xa64 fs/ext4/namei.c:3002
vfs_mkdir+0x334/0x4e4 fs/namei.c:4036
do_mkdirat+0x20c/0x610 fs/namei.c:4061
__do_sys_mkdirat fs/namei.c:4076 [inline]
__se_sys_mkdirat fs/namei.c:4074 [inline]
__arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4074
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
other info that might help us debug this:
Chain exists of:
&dquot->dq_lock --> &s->s_dquot.dqio_sem --> &ei->i_data_sem/2
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&ei->i_data_sem/2);
lock(&s->s_dquot.dqio_sem);
lock(&ei->i_data_sem/2);
lock(&dquot->dq_lock);
*** DEADLOCK ***
4 locks held by syz-executor.4/13272:
#0: ffff0000c1c6e460 (sb_writers#3){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0001041dac20 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:791 [inline]
#1: ffff0001041dac20 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: filename_create+0x200/0x464 fs/namei.c:3807
#2: ffff0000dcd85cd0 (&ei->i_data_sem/2){++++}-{3:3}, at: ext4_map_blocks+0x794/0x1884 fs/ext4/inode.c:644
#3: ffff800015a47728 (dquot_srcu){....}-{0:0}, at: rcu_lock_acquire+0x10/0x4c include/linux/rcupdate.h:303
stack backtrace:
CPU: 0 PID: 13272 Comm: syz-executor.4 Not tainted 6.1.15-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2055
check_noncircular+0x2cc/0x378 kernel/locking/lockdep.c:2177
check_prev_add kernel/locking/lockdep.c:3097 [inline]
check_prevs_add kernel/locking/lockdep.c:3216 [inline]
validate_chain kernel/locking/lockdep.c:3831 [inline]
__lock_acquire+0x3338/0x764c kernel/locking/lockdep.c:5055
lock_acquire+0x2f8/0x8dc kernel/locking/lockdep.c:5668
__mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
dquot_commit+0x54/0x240 fs/quota/dquot.c:479
ext4_write_dquot+0x1b0/0x284 fs/ext4/super.c:6724
ext4_mark_dquot_dirty+0xe8/0x140 fs/ext4/super.c:6772
mark_dquot_dirty fs/quota/dquot.c:346 [inline]
mark_all_dquot_dirty fs/quota/dquot.c:384 [inline]
__dquot_alloc_space+0x47c/0xd00 fs/quota/dquot.c:1722
dquot_alloc_space_nodirty include/linux/quotaops.h:300 [inline]
dquot_alloc_space include/linux/quotaops.h:313 [inline]
dquot_alloc_block include/linux/quotaops.h:337 [inline]
ext4_mb_new_blocks+0x1020/0x49c8 fs/ext4/mballoc.c:5573
ext4_ext_map_blocks+0x1740/0x688c fs/ext4/extents.c:4287
ext4_map_blocks+0x828/0x1884 fs/ext4/inode.c:651
ext4_getblk+0x198/0x6ec fs/ext4/inode.c:864
ext4_bread+0x3c/0x1b0 fs/ext4/inode.c:920
ext4_append+0x260/0x4cc fs/ext4/namei.c:83
ext4_init_new_dir+0x294/0x8e4 fs/ext4/namei.c:2956
ext4_mkdir+0x3d4/0xa64 fs/ext4/namei.c:3002
vfs_mkdir+0x334/0x4e4 fs/namei.c:4036
do_mkdirat+0x20c/0x610 fs/namei.c:4061
__do_sys_mkdirat fs/namei.c:4076 [inline]
__se_sys_mkdirat fs/namei.c:4074 [inline]
__arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4074
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
---
This report is generated by a bot. It may contain errors.
See
https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.