syzbot


possible deadlock in ext4_writepages

Status: upstream: reported syz repro on 2025/09/10 22:18
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+0bacd77c29cb89886c3a@syzkaller.appspotmail.com
First crash: 89d, last: 6h22m
Bug presence (1)
Date Name Commit Repro Result
2025/09/15 upstream (ToT) f83ec76bf285 syz [report] possible deadlock in ext4_writepages
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in ext4_writepages ext4 4 1 1213d 1209d 0/29 auto-obsoleted due to no activity on 2022/12/11 07:00
upstream possible deadlock in ext4_writepages (2) ext4 4 C unreliable 1691 5h47m 415d 0/29 upstream: reported C repro on 2024/10/19 20:27
linux-6.6 possible deadlock in ext4_writepages origin:upstream 4 syz 255 6h23m 87d 0/2 upstream: reported syz repro on 2025/09/12 16:06
linux-5.15 possible deadlock in ext4_writepages 4 2 949d 951d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:09
linux-5.15 possible deadlock in ext4_writepages (2) origin:upstream 4 syz 106 1h16m 89d 0/3 upstream: reported syz repro on 2025/09/10 19:34

Sample crash report:
loop0: detected capacity change from 0 to 512
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/4427 is trying to acquire lock:
ffff88801ca66b98 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1c0/0x2e50 fs/ext4/inode.c:2715

but task is already holding lock:
ffff88806ea65b10 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:162 [inline]
ffff88806ea65b10 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:6020 [inline]
ffff88806ea65b10 (&ei->xattr_sem){++++}-{3:3}, at: __ext4_mark_inode_dirty+0x3fe/0x770 fs/ext4/inode.c:6101

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&ei->xattr_sem){++++}-{3:3}:
       down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
       ext4_setattr+0x92a/0x19f0 fs/ext4/inode.c:5515
       notify_change+0xc74/0xf40 fs/attr.c:499
       chown_common+0x486/0x620 fs/open.c:736
       do_fchownat+0x164/0x270 fs/open.c:767
       __do_sys_chown fs/open.c:787 [inline]
       __se_sys_chown fs/open.c:785 [inline]
       __x64_sys_chown+0x7e/0x90 fs/open.c:785
       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 (jbd2_handle){++++}-{0:0}:
       start_this_handle+0x1f49/0x2150 fs/jbd2/transaction.c:463
       jbd2__journal_start+0x2b7/0x5a0 fs/jbd2/transaction.c:520
       __ext4_journal_start_sb+0x187/0x3d0 fs/ext4/ext4_jbd2.c:105
       __ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline]
       ext4_writepages+0xde7/0x2e50 fs/ext4/inode.c:2838
       do_writepages+0x3b7/0x610 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+0x137/0x200 mm/filemap.c:774
       ext4_sync_file+0x23b/0xca0 fs/ext4/fsync.c:151
       vfs_fsync_range fs/sync.c:188 [inline]
       vfs_fsync fs/sync.c:202 [inline]
       do_fsync fs/sync.c:212 [inline]
       __do_sys_fsync fs/sync.c:220 [inline]
       __se_sys_fsync fs/sync.c:218 [inline]
       __x64_sys_fsync+0x1a5/0x1e0 fs/sync.c:218
       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 (&sbi->s_writepages_rwsem){.+.+}-{0:0}:
       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
       percpu_down_read+0x44/0x1a0 include/linux/percpu-rwsem.h:51
       ext4_writepages+0x1c0/0x2e50 fs/ext4/inode.c:2715
       do_writepages+0x3b7/0x610 mm/page-writeback.c:2491
       __writeback_single_inode+0x156/0x1160 fs/fs-writeback.c:1622
       writeback_single_inode+0x221/0x8b0 fs/fs-writeback.c:1743
       write_inode_now+0x15d/0x1d0 fs/fs-writeback.c:2780
       iput_final fs/inode.c:1821 [inline]
       iput+0x613/0x980 fs/inode.c:1860
       ext4_xattr_block_set+0x2736/0x32a0 fs/ext4/xattr.c:2158
       ext4_xattr_move_to_block fs/ext4/xattr.c:2626 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2701 [inline]
       ext4_expand_extra_isize_ea+0x109b/0x19b0 fs/ext4/xattr.c:2793
       __ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:5980
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:6023 [inline]
       __ext4_mark_inode_dirty+0x47f/0x770 fs/ext4/inode.c:6101
       ext4_evict_inode+0xa73/0x1100 fs/ext4/inode.c:279
       evict+0x485/0x870 fs/inode.c:705
       ext4_orphan_cleanup+0xbd3/0x1400 fs/ext4/orphan.c:470
       __ext4_fill_super fs/ext4/super.c:5530 [inline]
       ext4_fill_super+0x7bdf/0x8150 fs/ext4/super.c:5661
       get_tree_bdev+0x3f1/0x610 fs/super.c:1366
       vfs_get_tree+0x88/0x270 fs/super.c:1573
       do_new_mount+0x24a/0xa40 fs/namespace.c:3078
       do_mount fs/namespace.c:3421 [inline]
       __do_sys_mount fs/namespace.c:3629 [inline]
       __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3606
       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:
  &sbi->s_writepages_rwsem --> jbd2_handle --> &ei->xattr_sem

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

3 locks held by syz.0.17/4427:
 #0: ffff88801ca640e0 (&type->s_umount_key#27/1){+.+.}-{3:3}, at: alloc_super+0x1fa/0x930 fs/super.c:228
 #1: ffff88801ca64650 (sb_internal){.+.+}-{0:0}, at: __sb_start_write include/linux/fs.h:1891 [inline]
 #1: ffff88801ca64650 (sb_internal){.+.+}-{0:0}, at: sb_start_intwrite include/linux/fs.h:2013 [inline]
 #1: ffff88801ca64650 (sb_internal){.+.+}-{0:0}, at: ext4_evict_inode+0x436/0x1100 fs/ext4/inode.c:240
 #2: ffff88806ea65b10 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:162 [inline]
 #2: ffff88806ea65b10 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:6020 [inline]
 #2: ffff88806ea65b10 (&ei->xattr_sem){++++}-{3:3}, at: __ext4_mark_inode_dirty+0x3fe/0x770 fs/ext4/inode.c:6101

stack backtrace:
CPU: 1 PID: 4427 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/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
 percpu_down_read+0x44/0x1a0 include/linux/percpu-rwsem.h:51
 ext4_writepages+0x1c0/0x2e50 fs/ext4/inode.c:2715
 do_writepages+0x3b7/0x610 mm/page-writeback.c:2491
 __writeback_single_inode+0x156/0x1160 fs/fs-writeback.c:1622
 writeback_single_inode+0x221/0x8b0 fs/fs-writeback.c:1743
 write_inode_now+0x15d/0x1d0 fs/fs-writeback.c:2780
 iput_final fs/inode.c:1821 [inline]
 iput+0x613/0x980 fs/inode.c:1860
 ext4_xattr_block_set+0x2736/0x32a0 fs/ext4/xattr.c:2158
 ext4_xattr_move_to_block fs/ext4/xattr.c:2626 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2701 [inline]
 ext4_expand_extra_isize_ea+0x109b/0x19b0 fs/ext4/xattr.c:2793
 __ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:5980
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:6023 [inline]
 __ext4_mark_inode_dirty+0x47f/0x770 fs/ext4/inode.c:6101
 ext4_evict_inode+0xa73/0x1100 fs/ext4/inode.c:279
 evict+0x485/0x870 fs/inode.c:705
 ext4_orphan_cleanup+0xbd3/0x1400 fs/ext4/orphan.c:470
 __ext4_fill_super fs/ext4/super.c:5530 [inline]
 ext4_fill_super+0x7bdf/0x8150 fs/ext4/super.c:5661
 get_tree_bdev+0x3f1/0x610 fs/super.c:1366
 vfs_get_tree+0x88/0x270 fs/super.c:1573
 do_new_mount+0x24a/0xa40 fs/namespace.c:3078
 do_mount fs/namespace.c:3421 [inline]
 __do_sys_mount fs/namespace.c:3629 [inline]
 __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3606
 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:0x7fdbb3790eea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007fff90cd6b88 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fff90cd6c10 RCX: 00007fdbb3790eea
RDX: 0000200000000180 RSI: 00002000000001c0 RDI: 00007fff90cd6bd0
RBP: 0000200000000180 R08: 00007fff90cd6c10 R09: 0000000000800700
R10: 0000000000800700 R11: 0000000000000246 R12: 00002000000001c0
R13: 00007fff90cd6bd0 R14: 000000000000046f R15: 000000000000002c
 </TASK>
EXT4-fs error (device loop0): ext4_xattr_inode_iget:404: inode #11: comm syz.0.17: iget: bad extra_isize 90 (inode size 256)
EXT4-fs (loop0): Remounting filesystem read-only
EXT4-fs error (device loop0): ext4_xattr_inode_iget:409: comm syz.0.17: error while reading EA inode 11 err=-117
EXT4-fs (loop0): Remounting filesystem read-only
EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2819: Unable to expand inode 15. Delete some EAs or run e2fsck.
EXT4-fs error (device loop0): ext4_xattr_inode_iget:404: inode #11: comm syz.0.17: iget: bad extra_isize 90 (inode size 256)
EXT4-fs (loop0): Remounting filesystem read-only
EXT4-fs error (device loop0): ext4_xattr_inode_iget:409: comm syz.0.17: error while reading EA inode 11 err=-117
EXT4-fs (loop0): Remounting filesystem read-only
EXT4-fs error (device loop0): ext4_xattr_inode_iget:404: inode #18: comm syz.0.17: iget: bad extra_isize 90 (inode size 256)
EXT4-fs (loop0): Remounting filesystem read-only
EXT4-fs error (device loop0): ext4_xattr_inode_iget:409: comm syz.0.17: error while reading EA inode 18 err=-117
EXT4-fs (loop0): Remounting filesystem read-only
EXT4-fs error (device loop0): ext4_xattr_inode_iget:404: inode #18: comm syz.0.17: iget: bad extra_isize 90 (inode size 256)
EXT4-fs (loop0): Remounting filesystem read-only
EXT4-fs error (device loop0): ext4_xattr_inode_iget:409: comm syz.0.17: error while reading EA inode 18 err=-117
EXT4-fs (loop0): Remounting filesystem read-only
EXT4-fs (loop0): 1 orphan inode deleted
EXT4-fs (loop0): mounted filesystem without journal. Quota mode: none.

Crashes (305):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/06 10:35 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/05 05:17 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/03 15:19 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/02 01:12 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/29 22:45 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/28 16:07 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/25 17:58 linux-6.1.y f6e38ae624cf 64219f15 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/10 04:56 linux-6.1.y f6e38ae624cf 4e1406b4 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/08 18:09 linux-6.1.y f6e38ae624cf 4e1406b4 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/07 09:14 linux-6.1.y f6e38ae624cf 4e1406b4 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/02 08:18 linux-6.1.y f6e38ae624cf 2c50b6a9 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/10/29 04:11 linux-6.1.y 8e6e2188d949 fd2207e7 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/10/27 11:27 linux-6.1.y 8e6e2188d949 c0460fcd .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/09/13 05:47 linux-6.1.y 3db754f56897 e2beed91 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/08 18:18 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/07 14:02 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/06 10:37 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/02 01:17 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/30 21:27 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/29 22:23 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/28 16:10 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/27 02:51 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/23 23:28 linux-6.1.y f6e38ae624cf 4fb8ef37 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/22 21:42 linux-6.1.y f6e38ae624cf 4fb8ef37 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/20 22:17 linux-6.1.y f6e38ae624cf 2cc4c24a .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/18 04:39 linux-6.1.y f6e38ae624cf ef766cd7 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/16 18:43 linux-6.1.y f6e38ae624cf f7988ea4 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/15 11:15 linux-6.1.y f6e38ae624cf f7988ea4 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/14 03:27 linux-6.1.y f6e38ae624cf 07e030de .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/13 00:55 linux-6.1.y f6e38ae624cf 07e030de .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/05 15:39 linux-6.1.y f6e38ae624cf a6c9c731 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/04 08:26 linux-6.1.y f6e38ae624cf 686bf657 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/02 08:13 linux-6.1.y f6e38ae624cf 2c50b6a9 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/10/31 07:26 linux-6.1.y f6e38ae624cf 2c50b6a9 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/10/27 10:50 linux-6.1.y 8e6e2188d949 c0460fcd .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/10/25 17:50 linux-6.1.y 8e6e2188d949 c0460fcd .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/10/25 17:37 linux-6.1.y 8e6e2188d949 c0460fcd .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/10/25 17:24 linux-6.1.y 8e6e2188d949 c0460fcd .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/10/25 17:22 linux-6.1.y 8e6e2188d949 c0460fcd .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/10/24 13:45 linux-6.1.y 8e6e2188d949 c0460fcd .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/10/23 06:57 linux-6.1.y 8e6e2188d949 c0460fcd .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/10/21 12:59 linux-6.1.y 8e6e2188d949 9832ed61 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/09/10 22:38 linux-6.1.y f97f1002271b fdeaa69b .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/07 16:32 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/06 16:11 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/06 06:47 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/05 04:57 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/04 06:49 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/03 14:35 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/02 09:47 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/02 07:50 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/02 00:50 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/01 09:19 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/30 09:28 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/28 15:29 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/27 19:59 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/27 15:31 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/26 13:09 linux-6.1.y f6e38ae624cf 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/26 11:46 linux-6.1.y f6e38ae624cf 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/25 21:01 linux-6.1.y f6e38ae624cf 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/25 01:12 linux-6.1.y f6e38ae624cf 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/11/24 22:17 linux-6.1.y f6e38ae624cf bf6fe8fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_writepages
2025/12/08 18:02 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/08 04:51 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/07 13:20 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/07 09:18 linux-6.1.y 50cbba13faa2 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/06 13:13 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/06 10:14 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/05 14:25 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/05 10:53 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/04 09:06 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/02 23:52 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/02 18:26 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/02 14:21 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/12/02 04:26 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/30 19:57 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/29 22:07 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/27 21:46 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/27 18:52 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/27 17:48 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/27 13:00 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/27 02:32 linux-6.1.y f6e38ae624cf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/26 04:40 linux-6.1.y f6e38ae624cf 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/25 19:17 linux-6.1.y f6e38ae624cf 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/11/24 20:59 linux-6.1.y f6e38ae624cf bf6fe8fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
2025/09/10 22:17 linux-6.1.y f97f1002271b fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_writepages
* Struck through repros no longer work on HEAD.