possible deadlock in ext4_move_extents (5)

Status: upstream: reported on 2026/07/07 04:52
Reported-by: syzbot+26d3afce5b19bd8d5c7d@syzkaller.appspotmail.com
First crash: 129d, last: 2d19h
▶ ▼ Similar bugs (10)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in ext4_move_extents 4 2 1198d 1287d 0/3 auto-obsoleted due to no activity on 2023/11/11 09:48
linux-6.1 possible deadlock in ext4_move_extents (3) 4 20 367d 749d 0/3 auto-obsoleted due to no activity on 2026/02/18 14:16
upstream possible deadlock in ext4_move_extents ext4 4 133 1298d 1468d 0/29 auto-obsoleted due to no activity on 2023/08/22 15:17
linux-6.1 possible deadlock in ext4_move_extents (2) 4 6 886d 1065d 0/3 auto-obsoleted due to no activity on 2024/09/18 11:30
linux-5.15 possible deadlock in ext4_move_extents 4 3 1223d 1299d 0/3 auto-obsoleted due to no activity on 2023/10/16 22:21
linux-5.15 possible deadlock in ext4_move_extents (5) 4 5 279d 381d 0/3 auto-obsoleted due to no activity on 2026/05/17 22:44
linux-6.1 possible deadlock in ext4_move_extents (4) 4 1 267d 267d 0/3 auto-obsoleted due to no activity on 2026/05/29 18:30
linux-5.15 possible deadlock in ext4_move_extents (2) 4 2 1025d 1095d 0/3 auto-obsoleted due to no activity on 2024/05/01 17:40
linux-5.15 possible deadlock in ext4_move_extents (3) 4 5 769d 898d 0/3 auto-obsoleted due to no activity on 2025/01/12 16:14
linux-5.15 possible deadlock in ext4_move_extents (4) 4 9 481d 649d 0/3 auto-obsoleted due to no activity on 2025/10/27 18:06

Sample crash report:
EXT4-fs: Quota format mount options ignored when QUOTA feature is enabled
EXT4-fs (loop2): mounted filesystem without journal. Quota mode: writeback.
ext4 filesystem being mounted at /200/file1 supports timestamps until 2038-01-19 (0x7fffffff)
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.2.891/7233 is trying to acquire lock:
ffff888055ba5cd0 (&ei->i_data_sem/1){+.+.}-{3:3}, at: ext4_move_extents+0x32b/0xbe0 fs/ext4/move_extent.c:615

but task is already holding lock:
ffff888055ba1698 (&ei->i_data_sem/2){++++}-{3:3}, at: ext4_double_down_write_data_sem+0x28/0x40 fs/ext4/move_extent.c:-1

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&ei->i_data_sem/2){++++}-{3:3}:
       down_write+0x36/0x60 kernel/locking/rwsem.c:1573
       ext4_map_blocks+0x914/0x1a90 fs/ext4/inode.c:674
       ext4_getblk+0x1c5/0x720 fs/ext4/inode.c:892
       ext4_bread+0x26/0x170 fs/ext4/inode.c:948
       ext4_quota_write+0x237/0x580 fs/ext4/super.c:7223
       write_blk fs/quota/quota_tree.c:70 [inline]
       find_free_dqentry+0x68c/0xc30 fs/quota/quota_tree.c:318
       do_insert_tree+0x717/0x1060 fs/quota/quota_tree.c:400
       do_insert_tree+0x9f5/0x1060 fs/quota/quota_tree.c:402
       do_insert_tree+0x9f5/0x1060 fs/quota/quota_tree.c:402
       do_insert_tree+0x9f5/0x1060 fs/quota/quota_tree.c:402
       dq_insert_tree fs/quota/quota_tree.c:432 [inline]
       qtree_write_dquot+0x49b/0x5d0 fs/quota/quota_tree.c:451
       v2_write_dquot+0x108/0x190 fs/quota/quota_v2.c:361
       dquot_acquire+0x2d5/0x520 fs/quota/dquot.c:500
       ext4_acquire_dquot+0x2e3/0x4a0 fs/ext4/super.c:6844
       dqget+0x713/0xbb0 fs/quota/dquot.c:1013
       __dquot_initialize+0x3a9/0xd00 fs/quota/dquot.c:1542
       ext4_process_orphan+0x4c/0x2e0 fs/ext4/orphan.c:327
       ext4_orphan_cleanup+0xdfe/0x1650 fs/ext4/orphan.c:472
       __ext4_fill_super fs/ext4/super.c:5578 [inline]
       ext4_fill_super+0x6cd4/0x77b0 fs/ext4/super.c:5700
       get_tree_bdev+0x3e6/0x610 fs/super.c:1377
       vfs_get_tree+0x88/0x270 fs/super.c:1584
       do_new_mount+0x247/0xa50 fs/namespace.c:3104
       do_mount fs/namespace.c:3475 [inline]
       __do_sys_mount fs/namespace.c:3683 [inline]
       __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3660
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #2 (&s->s_dquot.dqio_sem){++++}-{3:3}:
       down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
       v2_read_dquot+0x4a/0x110 fs/quota/quota_v2.c:335
       dquot_acquire+0x152/0x520 fs/quota/dquot.c:491
       ext4_acquire_dquot+0x2e3/0x4a0 fs/ext4/super.c:6844
       dqget+0x713/0xbb0 fs/quota/dquot.c:1013
       __dquot_initialize+0x3a9/0xd00 fs/quota/dquot.c:1542
       ext4_process_orphan+0x4c/0x2e0 fs/ext4/orphan.c:327
       ext4_orphan_cleanup+0xdfe/0x1650 fs/ext4/orphan.c:472
       __ext4_fill_super fs/ext4/super.c:5578 [inline]
       ext4_fill_super+0x6cd4/0x77b0 fs/ext4/super.c:5700
       get_tree_bdev+0x3e6/0x610 fs/super.c:1377
       vfs_get_tree+0x88/0x270 fs/super.c:1584
       do_new_mount+0x247/0xa50 fs/namespace.c:3104
       do_mount fs/namespace.c:3475 [inline]
       __do_sys_mount fs/namespace.c:3683 [inline]
       __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3660
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (&dquot->dq_lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12d/0xb40 kernel/locking/mutex.c:747
       dquot_commit+0x5a/0x410 fs/quota/dquot.c:535
       ext4_write_dquot+0x1f0/0x360 fs/ext4/super.c:6824
       mark_dquot_dirty fs/quota/dquot.c:400 [inline]
       mark_all_dquot_dirty+0xf9/0x400 fs/quota/dquot.c:440
       __dquot_free_space+0x7f8/0xbc0 fs/quota/dquot.c:1967
       dquot_free_space_nodirty include/linux/quotaops.h:372 [inline]
       dquot_free_space+0x1b/0x30 include/linux/quotaops.h:377
       swap_inode_boot_loader+0xc61/0x10f0 fs/ext4/ioctl.c:492
       __ext4_ioctl fs/ext4/ioctl.c:1438 [inline]
       ext4_ioctl+0x1e7a/0x41e0 fs/ext4/ioctl.c:1628
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&ei->i_data_sem/1){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3162 [inline]
       check_prevs_add kernel/locking/lockdep.c:3281 [inline]
       validate_chain kernel/locking/lockdep.c:3897 [inline]
       __lock_acquire+0x3a03/0x7ea0 kernel/locking/lockdep.c:5171
       lock_acquire+0x1bc/0x4a0 kernel/locking/lockdep.c:5790
       down_write_nested+0x39/0x60 kernel/locking/rwsem.c:1689
       ext4_move_extents+0x32b/0xbe0 fs/ext4/move_extent.c:615
       __ext4_ioctl fs/ext4/ioctl.c:1372 [inline]
       ext4_ioctl+0x3a3f/0x41e0 fs/ext4/ioctl.c:1628
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

Chain exists of:
  &ei->i_data_sem/1 --> &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(&ei->i_data_sem/1);

 *** DEADLOCK ***

4 locks held by syz.2.891/7233:
 #0: ffff88805ded6460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write_file+0x5c/0x200 fs/namespace.c:446
 #1: ffff888055ba1810 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:764 [inline]
 #1: ffff888055ba1810 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: lock_two_nondirectories+0xf7/0x150 fs/inode.c:1206
 #2: ffff888055ba5e48 (&sb->s_type->i_mutex_key#9/4){+.+.}-{3:3}, at: ext4_move_extents+0x310/0xbe0 fs/ext4/move_extent.c:608
 #3: ffff888055ba1698 (&ei->i_data_sem/2){++++}-{3:3}, at: ext4_double_down_write_data_sem+0x28/0x40 fs/ext4/move_extent.c:-1

stack backtrace:
CPU: 0 PID: 7233 Comm: syz.2.891 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 check_noncircular+0x2f8/0x400 kernel/locking/lockdep.c:2215
 check_prev_add kernel/locking/lockdep.c:3162 [inline]
 check_prevs_add kernel/locking/lockdep.c:3281 [inline]
 validate_chain kernel/locking/lockdep.c:3897 [inline]
 __lock_acquire+0x3a03/0x7ea0 kernel/locking/lockdep.c:5171
 lock_acquire+0x1bc/0x4a0 kernel/locking/lockdep.c:5790
 down_write_nested+0x39/0x60 kernel/locking/rwsem.c:1689
 ext4_move_extents+0x32b/0xbe0 fs/ext4/move_extent.c:615
 __ext4_ioctl fs/ext4/ioctl.c:1372 [inline]
 ext4_ioctl+0x3a3f/0x41e0 fs/ext4/ioctl.c:1628
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f52485a8f19
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f52494a1028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f5248825fa0 RCX: 00007f52485a8f19
RDX: 0000200000000040 RSI: 00000000c028660f RDI: 0000000000000005
RBP: 00007f5248637f6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f5248826038 R14: 00007f5248825fa0 R15: 00007ffd6f346e68
 </TASK>

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/10 18:03 linux-6.1.y c75b0cf0982c d3056657 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2026/11/05 10:40 linux-6.1.y 08889840163e 2ee8459f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2026/08/25 17:50 linux-6.1.y 05208478041c a9a1fc32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2026/07/07 04:52 linux-6.1.y 090666d3cc90 8e71ce95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
* Struck through repros no longer work on HEAD.