syzbot


possible deadlock in ext4_destroy_inline_data

Status: upstream: reported C repro on 2025/11/09 09:23
Reported-by: syzbot+ed8bb2474e55e323a784@syzkaller.appspotmail.com
First crash: 184d, last: 1h05m
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 4 198 15h32m 187d 0/3 upstream: reported on 2025/11/07 02:20
upstream possible deadlock in ext4_destroy_inline_data (2) ext4 4 C error 3208 now 188d 0/29 upstream: reported C repro on 2025/11/05 22:08
upstream possible deadlock in ext4_destroy_inline_data ext4 4 1 513d 509d 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 C 101 2h21m 192d 0/2 upstream: reported C repro on 2025/11/01 09:40

Sample crash report:
EXT4-fs error (device loop0): ext4_mb_generate_buddy:1126: group 0, block bitmap and bg descriptor inconsistent: 25 vs 1305 free clusters
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.19/4520 is trying to acquire lock:
ffff0000e5bc6518 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline]
ffff0000e5bc6518 (&ei->xattr_sem){++++}-{3:3}, at: ext4_destroy_inline_data+0x30/0x114 fs/ext4/inline.c:1922

but task is already holding lock:
ffff0000d638ec18 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1b8/0x28b4 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+0x70/0x2a8 include/linux/percpu-rwsem.h:51
       ext4_writepages+0x1b8/0x28b4 fs/ext4/inode.c:2717
       do_writepages+0x2b0/0x504 mm/page-writeback.c:2491
       __writeback_single_inode+0x164/0x1554 fs/fs-writeback.c:1622
       writeback_single_inode+0x1cc/0x740 fs/fs-writeback.c:1743
       write_inode_now+0x150/0x1cc fs/fs-writeback.c:2786
       iput_final fs/inode.c:1821 [inline]
       iput+0x5bc/0x7e4 fs/inode.c:1860
       ext4_xattr_block_set+0x1e9c/0x2880 fs/ext4/xattr.c:2093
       ext4_xattr_move_to_block fs/ext4/xattr.c:2611 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2686 [inline]
       ext4_expand_extra_isize_ea+0xe5c/0x17ac fs/ext4/xattr.c:2774
       __ext4_expand_extra_isize+0x298/0x358 fs/ext4/inode.c:6003
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:6046 [inline]
       __ext4_mark_inode_dirty+0x3e4/0x784 fs/ext4/inode.c:6124
       ext4_evict_inode+0xb64/0x1278 fs/ext4/inode.c:281
       evict+0x3e0/0x828 fs/inode.c:705
       iput_final fs/inode.c:1834 [inline]
       iput+0x754/0x7e4 fs/inode.c:1860
       ext4_process_orphan+0x240/0x2b4 fs/ext4/orphan.c:358
       ext4_orphan_cleanup+0x920/0x1060 fs/ext4/orphan.c:472
       __ext4_fill_super fs/ext4/super.c:5574 [inline]
       ext4_fill_super+0x594c/0x61b0 fs/ext4/super.c:5693
       get_tree_bdev+0x358/0x544 fs/super.c:1366
       ext4_get_tree+0x28/0x38 fs/ext4/super.c:5723
       vfs_get_tree+0x90/0x274 fs/super.c:1573
       do_new_mount+0x228/0x810 fs/namespace.c:3078
       path_mount+0x5bc/0xe80 fs/namespace.c:3408
       do_mount fs/namespace.c:3421 [inline]
       __do_sys_mount fs/namespace.c:3629 [inline]
       __se_sys_mount fs/namespace.c:3606 [inline]
       __arm64_sys_mount+0x49c/0x59c fs/namespace.c:3606
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

-> #0 (&ei->xattr_sem){++++}-{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+0x2880/0x6800 kernel/locking/lockdep.c:5049
       lock_acquire+0x20c/0x63c kernel/locking/lockdep.c:5662
       down_write+0x5c/0x88 kernel/locking/rwsem.c:1573
       ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline]
       ext4_destroy_inline_data+0x30/0x114 fs/ext4/inline.c:1922
       ext4_writepages+0x430/0x28b4 fs/ext4/inode.c:2763
       do_writepages+0x2b0/0x504 mm/page-writeback.c:2491
       filemap_fdatawrite_wbc+0x124/0x174 mm/filemap.c:388
       __filemap_fdatawrite_range mm/filemap.c:421 [inline]
       file_write_and_wait_range+0x11c/0x1f4 mm/filemap.c:774
       ext4_sync_file+0x210/0xc70 fs/ext4/fsync.c:151
       vfs_fsync_range+0x168/0x188 fs/sync.c:188
       generic_write_sync include/linux/fs.h:2962 [inline]
       ext4_buffered_write_iter+0x47c/0x528 fs/ext4/file.c:292
       ext4_file_write_iter+0x18c/0x1574 fs/ext4/file.c:-1
       call_write_iter include/linux/fs.h:2265 [inline]
       new_sync_write fs/read_write.c:491 [inline]
       vfs_write+0x3ec/0x7f0 fs/read_write.c:584
       ksys_write+0x12c/0x224 fs/read_write.c:637
       __do_sys_write fs/read_write.c:649 [inline]
       __se_sys_write fs/read_write.c:646 [inline]
       __arm64_sys_write+0x7c/0x90 fs/read_write.c:646
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

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.0.19/4520:
 #0: ffff0000d638c460 (sb_writers#3){.+.+}-{0:0}, at: vfs_write+0x244/0x7f0 fs/read_write.c:580
 #1: ffff0000d638ec18 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1b8/0x28b4 fs/ext4/inode.c:2717

stack backtrace:
CPU: 0 PID: 4520 Comm: syz.0.19 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call trace:
 dump_backtrace+0x1c0/0x1ec arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2048
 check_noncircular+0x264/0x2f8 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+0x2880/0x6800 kernel/locking/lockdep.c:5049
 lock_acquire+0x20c/0x63c kernel/locking/lockdep.c:5662
 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573
 ext4_write_lock_xattr fs/ext4/xattr.h:158 [inline]
 ext4_destroy_inline_data+0x30/0x114 fs/ext4/inline.c:1922
 ext4_writepages+0x430/0x28b4 fs/ext4/inode.c:2763
 do_writepages+0x2b0/0x504 mm/page-writeback.c:2491
 filemap_fdatawrite_wbc+0x124/0x174 mm/filemap.c:388
 __filemap_fdatawrite_range mm/filemap.c:421 [inline]
 file_write_and_wait_range+0x11c/0x1f4 mm/filemap.c:774
 ext4_sync_file+0x210/0xc70 fs/ext4/fsync.c:151
 vfs_fsync_range+0x168/0x188 fs/sync.c:188
 generic_write_sync include/linux/fs.h:2962 [inline]
 ext4_buffered_write_iter+0x47c/0x528 fs/ext4/file.c:292
 ext4_file_write_iter+0x18c/0x1574 fs/ext4/file.c:-1
 call_write_iter include/linux/fs.h:2265 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x3ec/0x7f0 fs/read_write.c:584
 ksys_write+0x12c/0x224 fs/read_write.c:637
 __do_sys_write fs/read_write.c:649 [inline]
 __se_sys_write fs/read_write.c:646 [inline]
 __arm64_sys_write+0x7c/0x90 fs/read_write.c:646
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
EXT4-fs (loop0): Delayed block allocation failed for inode 15 at logical offset 0 with max blocks 1 with error 28
EXT4-fs (loop0): This should not happen!! Data will be lost

EXT4-fs (loop0): Total free blocks count 0
EXT4-fs (loop0): Free/Dirty block details
EXT4-fs (loop0): free_blocks=20480
EXT4-fs (loop0): dirty_blocks=16
EXT4-fs (loop0): Block reservation details
EXT4-fs (loop0): i_reserved_data_blocks=1

Crashes (204):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
2026/05/13 03:48 linux-6.1.y ad16b162f21d a0949470 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/05/12 02:13 linux-6.1.y ad16b162f21d d168f260 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/05/12 00:25 linux-6.1.y ad16b162f21d d168f260 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/05/03 17:31 linux-6.1.y 4931e0e1673d a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/05/02 14:24 linux-6.1.y 4931e0e1673d a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/30 21:48 linux-6.1.y 4931e0e1673d a7464baf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/28 05:07 linux-6.1.y 7c87defbd336 ce741359 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/27 17:29 linux-6.1.y 7c87defbd336 0f700595 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/27 16:14 linux-6.1.y 7c87defbd336 0f700595 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/27 00:50 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/26 08:06 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/25 20:48 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/23 09:45 linux-6.1.y 7c87defbd336 b10da5ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/23 08:19 linux-6.1.y 7c87defbd336 b10da5ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/21 21:30 linux-6.1.y 7c87defbd336 0b6ab7ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_destroy_inline_data
2026/04/19 12:41 linux-6.1.y 7c87defbd336 303e2802 .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/05/12 13:56 linux-6.1.y ad16b162f21d 07aeade5 .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/11 10:24 linux-6.1.y ad16b162f21d 845acb1c .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/11 03:19 linux-6.1.y 128a674368bf 29233ece .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/09 21:05 linux-6.1.y 128a674368bf 29233ece .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/09 18:39 linux-6.1.y 128a674368bf 29233ece .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/05 08:13 linux-6.1.y 4931e0e1673d a898ba9c .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/05 05:46 linux-6.1.y 4931e0e1673d a898ba9c .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/04 07:16 linux-6.1.y 4931e0e1673d a0d91488 .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/03 09:10 linux-6.1.y 4931e0e1673d a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/28 22:48 linux-6.1.y 7c87defbd336 95008c03 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/28 06:19 linux-6.1.y 7c87defbd336 ce741359 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/27 14:49 linux-6.1.y 7c87defbd336 0f700595 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/27 07:22 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/26 14:01 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/26 11:58 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/26 05:57 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/26 01:19 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/25 14:59 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/25 12:40 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/25 11:00 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/25 08:28 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/25 03:31 linux-6.1.y 7c87defbd336 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/24 08:08 linux-6.1.y 7c87defbd336 9cfb3ca7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/23 03:22 linux-6.1.y 7c87defbd336 b10da5ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/22 01:37 linux-6.1.y 7c87defbd336 0b6ab7ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/21 11:24 linux-6.1.y 7c87defbd336 3f2e655b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/20 03:59 linux-6.1.y 7c87defbd336 303e2802 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
2026/04/18 00:49 linux-6.1.y 8e8fc038cad5 24ecfc1e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_destroy_inline_data
* Struck through repros no longer work on HEAD.