====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.3.944/7575 is trying to acquire lock: ffff888073c68268 (&dquot->dq_lock){+.+.}-{3:3}, at: dquot_commit+0x5a/0x410 fs/quota/dquot.c:532 but task is already holding lock: ffff88805c473e48 (&ei->i_data_sem/2){++++}-{3:3}, at: ext4_map_blocks+0x8c4/0x1a50 fs/ext4/inode.c:668 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+0x44/0x2e0 kernel/locking/rwsem.c:1498 ext4_map_blocks+0x350/0x1a50 fs/ext4/inode.c:600 ext4_getblk+0x176/0x670 fs/ext4/inode.c:872 ext4_bread+0x26/0x180 fs/ext4/inode.c:925 ext4_quota_read+0x1ac/0x390 fs/ext4/super.c:6577 read_blk fs/quota/quota_tree.c:55 [inline] find_tree_dqentry+0x187/0xb30 fs/quota/quota_tree.c:617 find_dqentry fs/quota/quota_tree.c:647 [inline] qtree_read_dquot+0x122/0x690 fs/quota/quota_tree.c:667 v2_read_dquot+0xc0/0x110 fs/quota/quota_v2.c:333 dquot_acquire+0x152/0x520 fs/quota/dquot.c:488 ext4_acquire_dquot+0x2e3/0x4a0 fs/ext4/super.c:6232 dqget+0x713/0xbb0 fs/quota/dquot.c:1010 __dquot_initialize+0x3a9/0xd00 fs/quota/dquot.c:1539 ext4_mkdir+0x198/0xc90 fs/ext4/namei.c:3061 vfs_mkdir+0x386/0x570 fs/namei.c:4116 do_mkdirat+0x1dd/0x5c0 fs/namei.c:4141 __do_sys_mkdirat fs/namei.c:4156 [inline] __se_sys_mkdirat fs/namei.c:4154 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4154 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #1 (&s->s_dquot.dqio_sem){++++}-{3:3}: down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 v2_read_dquot+0x4a/0x110 fs/quota/quota_v2.c:332 dquot_acquire+0x152/0x520 fs/quota/dquot.c:488 ext4_acquire_dquot+0x2e3/0x4a0 fs/ext4/super.c:6232 dqget+0x713/0xbb0 fs/quota/dquot.c:1010 __dquot_initialize+0x3a9/0xd00 fs/quota/dquot.c:1539 ext4_mkdir+0x198/0xc90 fs/ext4/namei.c:3061 vfs_mkdir+0x386/0x570 fs/namei.c:4116 do_mkdirat+0x1dd/0x5c0 fs/namei.c:4141 __do_sys_mkdirat fs/namei.c:4156 [inline] __se_sys_mkdirat fs/namei.c:4154 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4154 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #0 (&dquot->dq_lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5625 __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 dquot_commit+0x5a/0x410 fs/quota/dquot.c:532 ext4_write_dquot+0x1f0/0x360 fs/ext4/super.c:6212 mark_dquot_dirty fs/quota/dquot.c:397 [inline] mark_all_dquot_dirty+0xf9/0x400 fs/quota/dquot.c:437 __dquot_alloc_space+0x5cb/0xe10 fs/quota/dquot.c:1774 dquot_alloc_space_nodirty include/linux/quotaops.h:290 [inline] dquot_alloc_space include/linux/quotaops.h:303 [inline] dquot_alloc_block include/linux/quotaops.h:327 [inline] ext4_mb_new_blocks+0xf80/0x47c0 fs/ext4/mballoc.c:5750 ext4_ext_map_blocks+0x17d1/0x63d0 fs/ext4/extents.c:4372 ext4_map_blocks+0x97f/0x1a50 fs/ext4/inode.c:675 ext4_getblk+0x176/0x670 fs/ext4/inode.c:872 ext4_bread+0x26/0x180 fs/ext4/inode.c:925 ext4_append+0x2bb/0x560 fs/ext4/namei.c:83 ext4_add_entry+0xb61/0x1020 fs/ext4/namei.c:2513 ext4_mkdir+0x520/0xc90 fs/ext4/namei.c:3083 vfs_mkdir+0x386/0x570 fs/namei.c:4116 do_mkdirat+0x1dd/0x5c0 fs/namei.c:4141 __do_sys_mkdirat fs/namei.c:4156 [inline] __se_sys_mkdirat fs/namei.c:4154 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4154 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 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.3.944/7575: #0: ffff888078162460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:386 #1: ffff88805c473fc0 (&type->i_mutex_dir_key#4/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:828 [inline] #1: ffff88805c473fc0 (&type->i_mutex_dir_key#4/1){+.+.}-{3:3}, at: filename_create+0x20b/0x450 fs/namei.c:3886 #2: ffff88805c473e48 (&ei->i_data_sem/2){++++}-{3:3}, at: ext4_map_blocks+0x8c4/0x1a50 fs/ext4/inode.c:668 #3: ffffffff8c4418b8 (dquot_srcu){....}-{0:0}, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:312 stack backtrace: CPU: 0 PID: 7575 Comm: syz.3.944 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5625 __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 dquot_commit+0x5a/0x410 fs/quota/dquot.c:532 ext4_write_dquot+0x1f0/0x360 fs/ext4/super.c:6212 mark_dquot_dirty fs/quota/dquot.c:397 [inline] mark_all_dquot_dirty+0xf9/0x400 fs/quota/dquot.c:437 __dquot_alloc_space+0x5cb/0xe10 fs/quota/dquot.c:1774 dquot_alloc_space_nodirty include/linux/quotaops.h:290 [inline] dquot_alloc_space include/linux/quotaops.h:303 [inline] dquot_alloc_block include/linux/quotaops.h:327 [inline] ext4_mb_new_blocks+0xf80/0x47c0 fs/ext4/mballoc.c:5750 ext4_ext_map_blocks+0x17d1/0x63d0 fs/ext4/extents.c:4372 ext4_map_blocks+0x97f/0x1a50 fs/ext4/inode.c:675 ext4_getblk+0x176/0x670 fs/ext4/inode.c:872 ext4_bread+0x26/0x180 fs/ext4/inode.c:925 ext4_append+0x2bb/0x560 fs/ext4/namei.c:83 ext4_add_entry+0xb61/0x1020 fs/ext4/namei.c:2513 ext4_mkdir+0x520/0xc90 fs/ext4/namei.c:3083 vfs_mkdir+0x386/0x570 fs/namei.c:4116 do_mkdirat+0x1dd/0x5c0 fs/namei.c:4141 __do_sys_mkdirat fs/namei.c:4156 [inline] __se_sys_mkdirat fs/namei.c:4154 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4154 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7f7a99ae2fc7 Code: 00 66 90 48 89 f2 b9 00 01 00 00 48 89 fe bf 9c ff ff ff e9 db f7 ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 b8 02 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f7a97d1ae58 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007f7a97d1aee0 RCX: 00007f7a99ae2fc7 RDX: 00000000000001ff RSI: 0000200000000140 RDI: 00000000ffffff9c RBP: 0000000000000000 R08: 0000200000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000200000000140 R13: 00007f7a97d1aea0 R14: 0000000000000000 R15: 0000000000000000 EXT4-fs error (device loop3): ext4_do_update_inode:5229: inode #2: comm syz.3.944: corrupted inode contents EXT4-fs (loop3): Remounting filesystem read-only EXT4-fs error (device loop3): ext4_dirty_inode:6087: inode #2: comm syz.3.944: mark_inode_dirty error EXT4-fs (loop3): Remounting filesystem read-only EXT4-fs error (device loop3): ext4_do_update_inode:5229: inode #2: comm syz.3.944: corrupted inode contents EXT4-fs (loop3): Remounting filesystem read-only EXT4-fs error (device loop3): __ext4_ext_dirty:183: inode #2: comm syz.3.944: mark_inode_dirty error EXT4-fs (loop3): Remounting filesystem read-only EXT4-fs error (device loop3): ext4_do_update_inode:5229: inode #2: comm syz.3.944: corrupted inode contents EXT4-fs (loop3): Remounting filesystem read-only EXT4-fs error (device loop3): ext4_dirty_inode:6087: inode #2: comm syz.3.944: mark_inode_dirty error EXT4-fs (loop3): Remounting filesystem read-only