possible deadlock in ext4_destroy_inline_data

Status: fixed on 2026/11/10 01:49
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+ed8bb2474e55e323a784@syzkaller.appspotmail.com
Fix commit: 1dd4882dbdc8 ext4: skip extra isize expansion during mount to prevent deadlock
First crash: 369d, last: 61d
Fix bisection: fixed by (bisect log) :
commit 1dd4882dbdc8bfdf2182fa388883c143fac0902a
Author: Yun Zhou <yun.zhou@windriver.com>
Date: Tue Jun 23 06:19:02 2026 +0000

  ext4: skip extra isize expansion during mount to prevent deadlock

  
▶ ▼ Bug presence (2)
Date Name Commit Repro Result
2026/09/07 linux-6.1.y (ToT) cf82dcca9634 C [report] possible deadlock in ext4_destroy_inline_data
2026/09/07 upstream (ToT) df2908090cda C Didn't crash
▶ ▼ Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in ext4_destroy_inline_data origin:upstream 4 syz, C done 291 62d 371d 2/3 upstream: reported C repro on 2025/11/07 02:20
upstream possible deadlock in ext4_destroy_inline_data (2) prio:low ext4 4 syz, C error error 9790 71d 372d 0/29 upstream: reported C repro on 2025/11/05 22:08
upstream possible deadlock in ext4_destroy_inline_data ext4 4 1 698d 694d 0/29 auto-obsoleted due to no activity on 2025/03/25 12:07
linux-6.6 possible deadlock in ext4_destroy_inline_data origin:upstream 4 syz, C error 184 65d 377d 0/2 upstream: reported C repro on 2025/11/01 09:40

Sample crash report:
loop5: detected capacity change from 0 to 512
EXT4-fs (loop5): 1 truncate cleaned up
EXT4-fs (loop5): mounted filesystem without journal. Quota mode: none.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.5.583/7127 is trying to acquire lock:
ffff888071b514d8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline]
ffff888071b514d8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1930

but task is already holding lock:
ffff888149a8ec18 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x213/0x2e70 fs/ext4/inode.c:2717

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&sbi->s_writepages_rwsem){.+.+}-{0:0}:
       percpu_down_read+0x44/0x1a0 include/linux/percpu-rwsem.h:51
       ext4_writepages+0x213/0x2e70 fs/ext4/inode.c:2717
       do_writepages+0x3c6/0x640 mm/page-writeback.c:2491
       __writeback_single_inode+0x153/0x1170 fs/fs-writeback.c:1673
       writeback_single_inode+0x3d2/0x8e0 fs/fs-writeback.c:1794
       write_inode_now+0x17f/0x210 fs/fs-writeback.c:2837
       iput_final fs/inode.c:1821 [inline]
       iput+0x643/0x9c0 fs/inode.c:1860
       ext4_xattr_block_set+0x2239/0x2ff0 fs/ext4/xattr.c:2097
       ext4_xattr_move_to_block fs/ext4/xattr.c:2615 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2690 [inline]
       ext4_expand_extra_isize_ea+0x13d3/0x1d50 fs/ext4/xattr.c:2778
       __ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:6003
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:6046 [inline]
       __ext4_mark_inode_dirty+0x478/0x760 fs/ext4/inode.c:6124
       ext4_evict_inode+0xa67/0x10e0 fs/ext4/inode.c:281
       evict+0x4b6/0x8b0 fs/inode.c:705
       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

-> #0 (&ei->xattr_sem){++++}-{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+0x36/0x60 kernel/locking/rwsem.c:1573
       ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline]
       ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1930
       ext4_writepages+0x599/0x2e70 fs/ext4/inode.c:2763
       do_writepages+0x3c6/0x640 mm/page-writeback.c:2491
       filemap_fdatawrite_wbc+0x11e/0x180 mm/filemap.c:388
       __filemap_fdatawrite_range mm/filemap.c:421 [inline]
       file_write_and_wait_range+0x159/0x230 mm/filemap.c:774
       ext4_sync_file+0x22a/0xc30 fs/ext4/fsync.c:151
       generic_write_sync include/linux/fs.h:2973 [inline]
       ext4_buffered_write_iter+0x2de/0x380 fs/ext4/file.c:292
       ext4_file_write_iter+0x1e3/0x17d0 fs/ext4/file.c:-1
       call_write_iter include/linux/fs.h:2271 [inline]
       new_sync_write fs/read_write.c:491 [inline]
       vfs_write+0x482/0x9a0 fs/read_write.c:584
       ksys_pwrite64 fs/read_write.c:699 [inline]
       __do_sys_pwrite64 fs/read_write.c:709 [inline]
       __se_sys_pwrite64 fs/read_write.c:706 [inline]
       __x64_sys_pwrite64+0x194/0x220 fs/read_write.c:706
       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:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&sbi->s_writepages_rwsem);
                               lock(&ei->xattr_sem);
                               lock(&sbi->s_writepages_rwsem);
  lock(&ei->xattr_sem);

 *** DEADLOCK ***

2 locks held by syz.5.583/7127:
 #0: ffff888144b32460 (sb_writers#4){++++}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
 #1: ffff888149a8ec18 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x213/0x2e70 fs/ext4/inode.c:2717

stack backtrace:
CPU: 1 PID: 7127 Comm: syz.5.583 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+0x36/0x60 kernel/locking/rwsem.c:1573
 ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline]
 ext4_destroy_inline_data+0x24/0xe0 fs/ext4/inline.c:1930
 ext4_writepages+0x599/0x2e70 fs/ext4/inode.c:2763
 do_writepages+0x3c6/0x640 mm/page-writeback.c:2491
 filemap_fdatawrite_wbc+0x11e/0x180 mm/filemap.c:388
 __filemap_fdatawrite_range mm/filemap.c:421 [inline]
 file_write_and_wait_range+0x159/0x230 mm/filemap.c:774
 ext4_sync_file+0x22a/0xc30 fs/ext4/fsync.c:151
 generic_write_sync include/linux/fs.h:2973 [inline]
 ext4_buffered_write_iter+0x2de/0x380 fs/ext4/file.c:292
 ext4_file_write_iter+0x1e3/0x17d0 fs/ext4/file.c:-1
 call_write_iter include/linux/fs.h:2271 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x482/0x9a0 fs/read_write.c:584
 ksys_pwrite64 fs/read_write.c:699 [inline]
 __do_sys_pwrite64 fs/read_write.c:709 [inline]
 __se_sys_pwrite64 fs/read_write.c:706 [inline]
 __x64_sys_pwrite64+0x194/0x220 fs/read_write.c:706
 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:0x7f917259e159
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:00007f917353d028 EFLAGS: 00000246 ORIG_RAX: 0000000000000012
RAX: ffffffffffffffda RBX: 00007f9172825fa0 RCX: 00007f917259e159
RDX: 0000000000000001 RSI: 0000200000000140 RDI: 0000000000000004
RBP: 00007f9172635024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000008000c61 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f9172826038 R14: 00007f9172825fa0 R15: 00007fffd81049d8
 </TASK>
EXT4-fs error (device loop5): ext4_validate_block_bitmap:438: comm syz.5.583: bg 0: block 465: padding at end of block bitmap is not set
EXT4-fs (loop5): Remounting filesystem read-only

Crashes (398):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/04 17:17 linux-6.1.y cf82dcca9634 f65209a4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/09/01 13:22 linux-6.1.y d64a499eea6b 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/08/25 12:30 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_destroy_inline_data
2026/08/25 04:32 linux-6.1.y 05208478041c 614e416a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/08/14 22:37 linux-6.1.y e4f7d8be268e 6f9b3e89 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/08/13 15:09 linux-6.1.y e4f7d8be268e 359b2492 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/08/12 00:27 linux-6.1.y e4f7d8be268e 71790083 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/08/04 06:31 linux-6.1.y fb28aa725e05 9451e17e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/08/03 17:23 linux-6.1.y fb28aa725e05 6b7c9f71 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/08/01 10:40 linux-6.1.y fb28aa725e05 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/07/31 13:20 linux-6.1.y fb28aa725e05 7664cf44 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/07/31 13:20 linux-6.1.y fb28aa725e05 7664cf44 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/07/30 13:21 linux-6.1.y fb28aa725e05 2377cd3d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2025/11/09 09:22 linux-6.1.y f6e38ae624cf 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/09/12 22:42 linux-6.1.y cf82dcca9634 70a60e12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/09/09 19:37 linux-6.1.y cf82dcca9634 4e8b1cc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/09/09 06:34 linux-6.1.y cf82dcca9634 8387c273 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/09/08 07:18 linux-6.1.y cf82dcca9634 680aa3e1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/09/06 15:02 linux-6.1.y cf82dcca9634 4f7b22a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/09/05 15:17 linux-6.1.y cf82dcca9634 4f7b22a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/09/05 03:41 linux-6.1.y cf82dcca9634 4f7b22a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/09/04 20:22 linux-6.1.y cf82dcca9634 f65209a4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/09/04 12:19 linux-6.1.y cf82dcca9634 f65209a4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/09/03 10:31 linux-6.1.y cf82dcca9634 6a988719 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/31 19:23 linux-6.1.y d64a499eea6b 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/31 19:23 linux-6.1.y d64a499eea6b 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/31 11:17 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/30 12:16 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/30 04:42 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/29 14:55 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/28 15:54 linux-6.1.y d64a499eea6b e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/27 22:55 linux-6.1.y 79a9660d699e 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/27 20:54 linux-6.1.y 79a9660d699e 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/27 03:13 linux-6.1.y 05208478041c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/26 02:23 linux-6.1.y 05208478041c 6a91adb4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/24 09:20 linux-6.1.y 05208478041c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/24 03:22 linux-6.1.y 05208478041c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/23 16:27 linux-6.1.y 05208478041c 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/23 12:37 linux-6.1.y 7e6e67054721 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/17 16:02 linux-6.1.y e4f7d8be268e 905244d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/16 00:27 linux-6.1.y e4f7d8be268e 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/15 13:29 linux-6.1.y e4f7d8be268e 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/11 20:35 linux-6.1.y e4f7d8be268e 71790083 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/10 03:48 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/09 22:37 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/09 15:05 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/09 10:52 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/08/03 09:41 linux-6.1.y fb28aa725e05 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/07/31 06:56 linux-6.1.y fb28aa725e05 aaffb173 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/07/30 03:25 linux-6.1.y 1016ca6176ee 6ef5c1e2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/05/12 15:47 linux-6.1.y ad16b162f21d 07aeade5 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1 (corrupt fs)] [mounted in repro #2 (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
* Struck through repros no longer work on HEAD.