syzbot


possible deadlock in ext4_move_extents (3)

Status: upstream: reported on 2024/10/24 22:08
Reported-by: syzbot+4f2662aee9760cf70151@syzkaller.appspotmail.com
First crash: 273d, last: 1d13h
Similar bugs (7)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in ext4_move_extents 4 2 721d 810d 0/3 auto-obsoleted due to no activity on 2023/11/11 09:48
upstream possible deadlock in ext4_move_extents ext4 4 133 822d 992d 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 409d 588d 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 747d 822d 0/3 auto-obsoleted due to no activity on 2023/10/16 22:21
linux-5.15 possible deadlock in ext4_move_extents (2) 4 2 549d 619d 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 293d 422d 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 5d07h 173d 0/3 upstream: reported on 2025/02/01 20:02

Sample crash report:
EXT4-fs (loop0): mounted filesystem without journal. Quota mode: writeback.
ext4 filesystem being mounted at /128/file0 supports timestamps until 2038-01-19 (0x7fffffff)
======================================================
WARNING: possible circular locking dependency detected
6.1.146-syzkaller #0 Not tainted
------------------------------------------------------
syz.0.1764/10823 is trying to acquire lock:
ffff888054e4c8c0 (&ei->i_data_sem/1){+.+.}-{3:3}, at: ext4_move_extents+0x325/0xb90 fs/ext4/move_extent.c:615

but task is already holding lock:
ffff888054e4a0a0 (&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+0x903/0x1b60 fs/ext4/inode.c:672
       ext4_getblk+0x1ab/0x6d0 fs/ext4/inode.c:890
       ext4_bread+0x26/0x170 fs/ext4/inode.c:946
       ext4_quota_write+0x230/0x570 fs/ext4/super.c:7201
       write_blk fs/quota/quota_tree.c:70 [inline]
       find_free_dqentry+0x673/0xc20 fs/quota/quota_tree.c:318
       do_insert_tree+0x70d/0x1040 fs/quota/quota_tree.c:400
       do_insert_tree+0x9ae/0x1040 fs/quota/quota_tree.c:402
       do_insert_tree+0x9ae/0x1040 fs/quota/quota_tree.c:402
       do_insert_tree+0x9ae/0x1040 fs/quota/quota_tree.c:402
       dq_insert_tree fs/quota/quota_tree.c:432 [inline]
       qtree_write_dquot+0x48d/0x5b0 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:472
       ext4_acquire_dquot+0x2d9/0x4a0 fs/ext4/super.c:6810
       dqget+0x778/0xeb0 fs/quota/dquot.c:988
       dquot_set_dqblk+0x27/0xf90 fs/quota/dquot.c:2833
       quota_setquota+0x4ac/0x530 fs/quota/quota.c:310
       __do_sys_quotactl fs/quota/quota.c:960 [inline]
       __se_sys_quotactl+0x295/0x6b0 fs/quota/quota.c:916
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       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:463
       ext4_acquire_dquot+0x2d9/0x4a0 fs/ext4/super.c:6810
       dqget+0x778/0xeb0 fs/quota/dquot.c:988
       __dquot_initialize+0x3b6/0xcb0 fs/quota/dquot.c:1517
       ext4_mkdir+0x16c/0xc50 fs/ext4/namei.c:3059
       vfs_mkdir+0x387/0x570 fs/namei.c:4106
       do_mkdirat+0x1d0/0x430 fs/namei.c:4131
       __do_sys_mkdirat fs/namei.c:4146 [inline]
       __se_sys_mkdirat fs/namei.c:4144 [inline]
       __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4144
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (&dquot->dq_lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747
       dquot_commit+0x5a/0x410 fs/quota/dquot.c:507
       ext4_write_dquot+0x1f0/0x360 fs/ext4/super.c:6790
       mark_dquot_dirty fs/quota/dquot.c:372 [inline]
       mark_all_dquot_dirty+0x1e3/0x400 fs/quota/dquot.c:412
       __dquot_free_space+0x7ec/0xbc0 fs/quota/dquot.c:1942
       dquot_free_space_nodirty include/linux/quotaops.h:379 [inline]
       dquot_free_space+0x1b/0x30 include/linux/quotaops.h:384
       swap_inode_boot_loader+0xc77/0x1100 fs/ext4/ioctl.c:492
       __ext4_ioctl fs/ext4/ioctl.c:1424 [inline]
       ext4_ioctl+0x1bd0/0x3dd0 fs/ext4/ioctl.c:1614
       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:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&ei->i_data_sem/1){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain kernel/locking/lockdep.c:3825 [inline]
       __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
       lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
       down_write_nested+0x39/0x60 kernel/locking/rwsem.c:1689
       ext4_move_extents+0x325/0xb90 fs/ext4/move_extent.c:615
       __ext4_ioctl fs/ext4/ioctl.c:1358 [inline]
       ext4_ioctl+0x3501/0x3dd0 fs/ext4/ioctl.c:1614
       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:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       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.0.1764/10823:
 #0: ffff888057910460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write_file+0x5c/0x200 fs/namespace.c:437
 #1: ffff888054e4a218 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
 #1: ffff888054e4a218 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: lock_two_nondirectories+0xd5/0x150 fs/inode.c:1208
 #2: ffff888054e4ca38 (&sb->s_type->i_mutex_key#8/4){+.+.}-{3:3}, at: ext4_move_extents+0x30a/0xb90 fs/ext4/move_extent.c:608
 #3: ffff888054e4a0a0 (&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: 1 PID: 10823 Comm: syz.0.1764 Not tainted 6.1.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3090 [inline]
 check_prevs_add kernel/locking/lockdep.c:3209 [inline]
 validate_chain kernel/locking/lockdep.c:3825 [inline]
 __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
 down_write_nested+0x39/0x60 kernel/locking/rwsem.c:1689
 ext4_move_extents+0x325/0xb90 fs/ext4/move_extent.c:615
 __ext4_ioctl fs/ext4/ioctl.c:1358 [inline]
 ext4_ioctl+0x3501/0x3dd0 fs/ext4/ioctl.c:1614
 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:51 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fbf0818e9a9
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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbf08f52038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fbf083b5fa0 RCX: 00007fbf0818e9a9
RDX: 0000200000000040 RSI: 00000000c028660f RDI: 0000000000000005
RBP: 00007fbf08210d69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fbf083b5fa0 R15: 00007ffc8c32fdf8
 </TASK>

Crashes (16):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/23 11:26 linux-6.1.y 3369c6df2fae e1dd4f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2025/07/16 11:16 linux-6.1.y f2198ea7eb3e 124ec9cc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2025/07/08 22:07 linux-6.1.y 04d1ccaa9c28 4d9fdfa4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2025/07/03 07:50 linux-6.1.y 7e69c33e4858 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2025/05/15 09:38 linux-6.1.y 02b72ccb5f9d d6b2ee52 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2025/03/22 20:52 linux-6.1.y 344a09659766 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2025/03/09 18:58 linux-6.1.y 6ae7ac5c4251 163f510d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2025/03/06 20:05 linux-6.1.y 3a8358583626 831e3629 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2025/03/06 20:05 linux-6.1.y 3a8358583626 831e3629 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2025/02/18 07:09 linux-6.1.y 0cbb5f65e52f 429ea007 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2025/02/15 07:37 linux-6.1.y 0cbb5f65e52f 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2024/12/11 21:56 linux-6.1.y e4d90d63d385 ff949d25 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2024/12/11 05:02 linux-6.1.y e4d90d63d385 cfc402b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2024/12/08 04:53 linux-6.1.y e4d90d63d385 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2024/12/07 23:23 linux-6.1.y e4d90d63d385 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_move_extents
2024/10/24 22:07 linux-6.1.y 7ec6f9fa3d97 0d144d1a .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.