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: 52d, last: 2d20h
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 1121d 1210d 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 290d 672d 0/3 auto-obsoleted due to no activity on 2026/02/18 14:16
upstream possible deadlock in ext4_move_extents ext4 4 133 1221d 1391d 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 809d 988d 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 1146d 1222d 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 202d 304d 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 190d 190d 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 948d 1018d 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 692d 821d 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 404d 572d 0/3 auto-obsoleted due to no activity on 2025/10/27 18:06

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.8.1341/9934 is trying to acquire lock:
ffff888056055cd0 (&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:
ffff8880560552c8 (&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_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
       ext4_map_blocks+0x338/0x1a90 fs/ext4/inode.c:606
       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:7228
       write_blk fs/quota/quota_tree.c:70 [inline]
       get_free_dqblk+0x2dc/0x630 fs/quota/quota_tree.c:136
       do_insert_tree+0x22b/0x1060 fs/quota/quota_tree.c:347
       do_insert_tree+0x9f5/0x1060 fs/quota/quota_tree.c:402
       do_insert_tree+0x9b8/0x1060 fs/quota/quota_tree.c:402
       do_insert_tree+0x9b8/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:6837
       dqget+0x713/0xbb0 fs/quota/dquot.c:1013
       __dquot_initialize+0x324/0xd00 fs/quota/dquot.c:1542
       ext4_xattr_set+0xc5/0x310 fs/ext4/xattr.c:2487
       __vfs_setxattr+0x3d8/0x410 fs/xattr.c:182
       __vfs_setxattr_noperm+0x126/0x5e0 fs/xattr.c:216
       vfs_setxattr+0x167/0x2e0 fs/xattr.c:309
       ovl_do_setxattr fs/overlayfs/overlayfs.h:252 [inline]
       ovl_setxattr fs/overlayfs/overlayfs.h:264 [inline]
       ovl_verify_set_fh+0x1a8/0x410 fs/overlayfs/namei.c:473
       ovl_verify_origin fs/overlayfs/overlayfs.h:545 [inline]
       ovl_get_indexdir+0x170/0x610 fs/overlayfs/super.c:1559
       ovl_fill_super+0x348a/0x42f0 fs/overlayfs/super.c:2120
       mount_nodev+0x52/0xe0 fs/super.c:1500
       legacy_get_tree+0xe6/0x180 fs/fs_context.c:632
       vfs_get_tree+0x88/0x270 fs/super.c:1584
       do_new_mount+0x247/0xa40 fs/namespace.c:3078
       do_mount fs/namespace.c:3421 [inline]
       __do_sys_mount fs/namespace.c:3629 [inline]
       __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3606
       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:6837
       dqget+0x713/0xbb0 fs/quota/dquot.c:1013
       __dquot_initialize+0x324/0xd00 fs/quota/dquot.c:1542
       ext4_process_orphan+0x4c/0x2e0 fs/ext4/orphan.c:327
       ext4_orphan_cleanup+0xc32/0x1470 fs/ext4/orphan.c:472
       __ext4_fill_super fs/ext4/super.c:5574 [inline]
       ext4_fill_super+0x6f0c/0x78f0 fs/ext4/super.c:5693
       get_tree_bdev+0x3e6/0x610 fs/super.c:1377
       vfs_get_tree+0x88/0x270 fs/super.c:1584
       do_new_mount+0x247/0xa40 fs/namespace.c:3078
       do_mount fs/namespace.c:3421 [inline]
       __do_sys_mount fs/namespace.c:3629 [inline]
       __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3606
       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/0xae0 kernel/locking/mutex.c:747
       dquot_commit+0x5a/0x410 fs/quota/dquot.c:535
       ext4_write_dquot+0x1f0/0x360 fs/ext4/super.c:6817
       mark_dquot_dirty fs/quota/dquot.c:400 [inline]
       mark_all_dquot_dirty+0xf9/0x400 fs/quota/dquot.c:440
       __dquot_alloc_space+0x5f6/0xe50 fs/quota/dquot.c:1777
       dquot_alloc_space_nodirty include/linux/quotaops.h:293 [inline]
       dquot_alloc_space include/linux/quotaops.h:306 [inline]
       dquot_alloc_block include/linux/quotaops.h:330 [inline]
       ext4_mb_new_blocks+0xf55/0x44d0 fs/ext4/mballoc.c:5740
       ext4_new_meta_blocks+0x172/0x3d0 fs/ext4/balloc.c:739
       ext4_ext_grow_indepth fs/ext4/extents.c:1331 [inline]
       ext4_ext_create_new_leaf fs/ext4/extents.c:1437 [inline]
       ext4_ext_insert_extent+0x101d/0x47d0 fs/ext4/extents.c:2120
       ext4_split_extent_at+0x7c4/0xf80 fs/ext4/extents.c:3254
       ext4_force_split_extent_at fs/ext4/extents.c:338 [inline]
       ext4_swap_extents+0x772/0x1d60 fs/ext4/extents.c:5769
       move_extent_per_page+0x1f9b/0x48e0 fs/ext4/move_extent.c:367
       ext4_move_extents+0x8e1/0xbe0 fs/ext4/move_extent.c:678
       __ext4_ioctl fs/ext4/ioctl.c:1367 [inline]
       ext4_ioctl+0x37d6/0x4120 fs/ext4/ioctl.c:1623
       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:3095 [inline]
       check_prevs_add kernel/locking/lockdep.c:3214 [inline]
       validate_chain kernel/locking/lockdep.c:3830 [inline]
       __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
       lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
       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:1367 [inline]
       ext4_ioctl+0x37d6/0x4120 fs/ext4/ioctl.c:1623
       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.8.1341/9934:
 #0: ffff8880407de460 (sb_writers#4){++++}-{0:0}, at: mnt_want_write_file+0x5c/0x200 fs/namespace.c:446
 #1: ffff888056055440 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:764 [inline]
 #1: ffff888056055440 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: lock_two_nondirectories+0xf7/0x150 fs/inode.c:1208
 #2: ffff888056055e48 (&sb->s_type->i_mutex_key#9/4){+.+.}-{3:3}, at: ext4_move_extents+0x310/0xbe0 fs/ext4/move_extent.c:608
 #3: ffff8880560552c8 (&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: 9934 Comm: syz.8.1341 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3095 [inline]
 check_prevs_add kernel/locking/lockdep.c:3214 [inline]
 validate_chain kernel/locking/lockdep.c:3830 [inline]
 __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
 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:1367 [inline]
 ext4_ioctl+0x37d6/0x4120 fs/ext4/ioctl.c:1623
 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:0x7f1a7139e0d9
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:00007f1a72306028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f1a71625fa0 RCX: 00007f1a7139e0d9
RDX: 0000200000000040 RSI: 00000000c028660f RDI: 0000000000000005
RBP: 00007f1a71435024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1a71626038 R14: 00007f1a71625fa0 R15: 00007ffcdc3bdef8
 </TASK>
EXT4-fs (loop8): unmounting filesystem.

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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.