syzbot


possible deadlock in ext4_writepages (2)

Status: upstream: reported C repro on 2025/09/10 19:34
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+4e957072bdc454795418@syzkaller.appspotmail.com
First crash: 197d, last: 5h27m
Bug presence (1)
Date Name Commit Repro Result
2026/03/22 upstream (ToT) 113ae7b4decc C [report] possible deadlock in ext4_writepages
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in ext4_writepages 4 C 695 6h49m 197d 0/3 upstream: reported C repro on 2025/09/10 22:18
upstream possible deadlock in ext4_writepages ext4 4 1 1321d 1317d 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 4812 30m 523d 0/29 upstream: reported C repro on 2024/10/19 20:27
linux-6.6 possible deadlock in ext4_writepages origin:upstream 4 syz 521 1d22h 195d 0/2 upstream: reported syz repro on 2025/09/12 16:06
linux-5.15 possible deadlock in ext4_writepages 4 2 1058d 1059d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:09
Last patch testing requests (2)
Created Duration User Patch Repo Result
2025/09/25 12:32 14m retest repro linux-5.15.y report log
2025/09/25 12:32 13m retest repro linux-5.15.y report log

Sample crash report:
EXT4-fs (loop0): Ignoring removed bh option
EXT4-fs (loop0): Warning: mounting with an experimental mount option 'dioread_nolock' for blocksize < PAGE_SIZE
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.51/4408 is trying to acquire lock:
ffff88801f406bd8 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x20f/0x2df0 fs/ext4/inode.c:2689

but task is already holding lock:
ffff88805ea89eb0 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:165 [inline]
ffff88805ea89eb0 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:5945 [inline]
ffff88805ea89eb0 (&ei->xattr_sem){++++}-{3:3}, at: __ext4_mark_inode_dirty+0x3e8/0x700 fs/ext4/inode.c:6026

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ei->xattr_sem){++++}-{3:3}:
       down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498
       ext4_xattr_get+0xfc/0x800 fs/ext4/xattr.c:654
       ext4_get_acl+0x80/0x660 fs/ext4/acl.c:165
       get_acl+0x154/0x250 fs/posix_acl.c:153
       posix_acl_create+0x124/0x430 fs/posix_acl.c:632
       ext4_init_acl+0xb7/0x330 fs/ext4/acl.c:283
       __ext4_new_inode+0x2eb3/0x3a40 fs/ext4/ialloc.c:1328
       ext4_ext_migrate+0x5f1/0xe60 fs/ext4/migrate.c:456
       __ext4_ioctl fs/ext4/ioctl.c:1031 [inline]
       ext4_ioctl+0x1a84/0x3870 fs/ext4/ioctl.c:1285
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c42/0x7d10 kernel/locking/lockdep.c:5012
       lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
       percpu_down_read+0x46/0x1b0 include/linux/percpu-rwsem.h:51
       ext4_writepages+0x20f/0x2df0 fs/ext4/inode.c:2689
       do_writepages+0x476/0x6e0 mm/page-writeback.c:2386
       __writeback_single_inode+0x153/0xda0 fs/fs-writeback.c:1657
       writeback_single_inode+0x3cb/0x8e0 fs/fs-writeback.c:1770
       write_inode_now+0x23b/0x2c0 fs/fs-writeback.c:2817
       iput_final fs/inode.c:1756 [inline]
       iput+0x5ab/0x8a0 fs/inode.c:1795
       ext4_xattr_set_entry+0x34f4/0x3ea0 fs/ext4/xattr.c:1825
       ext4_xattr_block_set+0x4fd/0x2d20 fs/ext4/xattr.c:1924
       ext4_xattr_move_to_block fs/ext4/xattr.c:2618 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2693 [inline]
       ext4_expand_extra_isize_ea+0xf3f/0x19b0 fs/ext4/xattr.c:2781
       __ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:5905
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:5948 [inline]
       __ext4_mark_inode_dirty+0x469/0x700 fs/ext4/inode.c:6026
       ext4_evict_inode+0xa8d/0x1090 fs/ext4/inode.c:282
       evict+0x4c9/0x8d0 fs/inode.c:647
       ext4_orphan_cleanup+0xad2/0x1320 fs/ext4/orphan.c:472
       ext4_fill_super+0x8e25/0x95a0 fs/ext4/super.c:5000
       mount_bdev+0x287/0x3c0 fs/super.c:1400
       legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
       vfs_get_tree+0x88/0x270 fs/super.c:1530
       do_new_mount+0x24a/0xa40 fs/namespace.c:3034
       do_mount fs/namespace.c:3377 [inline]
       __do_sys_mount fs/namespace.c:3585 [inline]
       __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

3 locks held by syz.0.51/4408:
 #0: ffff88801f4040e0 (&type->s_umount_key#28/1){+.+.}-{3:3}, at: alloc_super+0x201/0x950 fs/super.c:229
 #1: ffff88801f404650 (sb_internal){.+.+}-{0:0}, at: __sb_start_write include/linux/fs.h:1811 [inline]
 #1: ffff88801f404650 (sb_internal){.+.+}-{0:0}, at: sb_start_intwrite include/linux/fs.h:1928 [inline]
 #1: ffff88801f404650 (sb_internal){.+.+}-{0:0}, at: ext4_evict_inode+0x44a/0x1090 fs/ext4/inode.c:243
 #2: ffff88805ea89eb0 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:165 [inline]
 #2: ffff88805ea89eb0 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:5945 [inline]
 #2: ffff88805ea89eb0 (&ei->xattr_sem){++++}-{3:3}, at: __ext4_mark_inode_dirty+0x3e8/0x700 fs/ext4/inode.c:6026

stack backtrace:
CPU: 1 PID: 4408 Comm: syz.0.51 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c42/0x7d10 kernel/locking/lockdep.c:5012
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 percpu_down_read+0x46/0x1b0 include/linux/percpu-rwsem.h:51
 ext4_writepages+0x20f/0x2df0 fs/ext4/inode.c:2689
 do_writepages+0x476/0x6e0 mm/page-writeback.c:2386
 __writeback_single_inode+0x153/0xda0 fs/fs-writeback.c:1657
 writeback_single_inode+0x3cb/0x8e0 fs/fs-writeback.c:1770
 write_inode_now+0x23b/0x2c0 fs/fs-writeback.c:2817
 iput_final fs/inode.c:1756 [inline]
 iput+0x5ab/0x8a0 fs/inode.c:1795
 ext4_xattr_set_entry+0x34f4/0x3ea0 fs/ext4/xattr.c:1825
 ext4_xattr_block_set+0x4fd/0x2d20 fs/ext4/xattr.c:1924
 ext4_xattr_move_to_block fs/ext4/xattr.c:2618 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2693 [inline]
 ext4_expand_extra_isize_ea+0xf3f/0x19b0 fs/ext4/xattr.c:2781
 __ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:5905
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5948 [inline]
 __ext4_mark_inode_dirty+0x469/0x700 fs/ext4/inode.c:6026
 ext4_evict_inode+0xa8d/0x1090 fs/ext4/inode.c:282
 evict+0x4c9/0x8d0 fs/inode.c:647
 ext4_orphan_cleanup+0xad2/0x1320 fs/ext4/orphan.c:472
 ext4_fill_super+0x8e25/0x95a0 fs/ext4/super.c:5000
 mount_bdev+0x287/0x3c0 fs/super.c:1400
 legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x24a/0xa40 fs/namespace.c:3034
 do_mount fs/namespace.c:3377 [inline]
 __do_sys_mount fs/namespace.c:3585 [inline]
 __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f9a0e652a0a
Code: 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe975d5438 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffe975d54c0 RCX: 00007f9a0e652a0a
RDX: 0000200000000180 RSI: 0000200000000000 RDI: 00007ffe975d5480
RBP: 0000200000000180 R08: 00007ffe975d54c0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000200000000000
R13: 00007ffe975d5480 R14: 000000000000047a R15: 0000200000000b40
 </TASK>
EXT4-fs error (device loop0): ext4_xattr_inode_iget:401: inode #11: comm syz.0.51: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop0): ext4_xattr_inode_iget:406: comm syz.0.51: error while reading EA inode 11 err=-117
EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2807: Unable to expand inode 15. Delete some EAs or run e2fsck.
EXT4-fs error (device loop0): ext4_xattr_inode_iget:401: inode #11: comm syz.0.51: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop0): ext4_xattr_inode_iget:406: comm syz.0.51: error while reading EA inode 11 err=-117
EXT4-fs error (device loop0): ext4_xattr_inode_iget:401: inode #18: comm syz.0.51: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop0): ext4_xattr_inode_iget:406: comm syz.0.51: error while reading EA inode 18 err=-117
EXT4-fs error (device loop0): ext4_xattr_inode_iget:401: inode #18: comm syz.0.51: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop0): ext4_xattr_inode_iget:406: comm syz.0.51: error while reading EA inode 18 err=-117
EXT4-fs (loop0): 1 orphan inode deleted
EXT4-fs (loop0): mounted filesystem without journal. Opts: data_err=ignore,dioread_nolock,debug_want_extra_isize=0x000000000000005a,prjquota,max_dir_size_kb=0x0000000000000004,bh,min_batch_time=0x0000000000000003,,errors=continue. Quota mode: writeback.

Crashes (364):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/03/22 13:08 linux-5.15.y 91d48252ad4b 5b92003d .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1 (clean fs)] [mounted in repro #2 (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/18 06:45 linux-5.15.y 68efe5a6c16a 20d37d28 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/15 01:12 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/12 22:52 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/11 17:26 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/10 01:00 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/08 22:31 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/07 21:47 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/06 15:56 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/05 10:52 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/03 05:14 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/02 03:35 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/01/01 01:13 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/30 19:56 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/29 15:56 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/29 09:56 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/28 01:11 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/27 04:37 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/26 03:51 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/24 21:34 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/22 02:56 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/20 18:20 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/20 06:38 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/18 17:19 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/17 09:51 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/15 18:57 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/13 13:14 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/12 10:04 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/11 01:05 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/09 19:15 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/08 18:18 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/07 13:42 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/06 07:27 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/03 09:54 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/12/01 18:02 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/11/30 15:39 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/11/26 12:46 linux-5.15.y cc5ec8769306 64219f15 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/11/26 11:25 linux-5.15.y cc5ec8769306 64219f15 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/11/26 10:18 linux-5.15.y cc5ec8769306 64219f15 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/11/24 01:38 linux-5.15.y cc5ec8769306 4fb8ef37 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/11/22 08:06 linux-5.15.y cc5ec8769306 4fb8ef37 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/09/10 20:44 linux-5.15.y de9476bb4f1b fdeaa69b .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2025/09/10 19:34 linux-5.15.y de9476bb4f1b fdeaa69b .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/27 01:07 linux-5.15.y 91d48252ad4b 766b6434 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/26 17:17 linux-5.15.y 91d48252ad4b 766b6434 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/26 02:46 linux-5.15.y 91d48252ad4b c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/26 02:46 linux-5.15.y 91d48252ad4b c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/24 22:19 linux-5.15.y 91d48252ad4b 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/24 07:14 linux-5.15.y 91d48252ad4b baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/23 04:34 linux-5.15.y 91d48252ad4b 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/23 01:18 linux-5.15.y 91d48252ad4b 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/22 11:34 linux-5.15.y 91d48252ad4b 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/21 20:35 linux-5.15.y 91d48252ad4b 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/20 23:04 linux-5.15.y 91d48252ad4b ac6f1dff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/20 08:44 linux-5.15.y 91d48252ad4b 2f245add .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/20 00:07 linux-5.15.y 91d48252ad4b bd6dcb30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/18 17:19 linux-5.15.y 91d48252ad4b 0199f9a1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/18 09:28 linux-5.15.y 91d48252ad4b c8810548 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/17 16:00 linux-5.15.y 91d48252ad4b c01bca74 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/12 16:51 linux-5.15.y 91d48252ad4b 4efadf07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/11 23:55 linux-5.15.y 91d48252ad4b 2d88ab01 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/11 09:21 linux-5.15.y 91d48252ad4b 86914af9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/10 20:33 linux-5.15.y 91d48252ad4b 4683d576 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/09 13:16 linux-5.15.y 91d48252ad4b 176bead5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/09 08:56 linux-5.15.y 91d48252ad4b 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/08 20:07 linux-5.15.y 91d48252ad4b 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/06 05:24 linux-5.15.y 91d48252ad4b 31e9c887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/05 11:41 linux-5.15.y 91d48252ad4b d20b04c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/05 04:35 linux-5.15.y 91d48252ad4b a9fe5c9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/02 09:21 linux-5.15.y 3330a8d33e08 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/03/01 12:46 linux-5.15.y 3330a8d33e08 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/28 08:50 linux-5.15.y 3330a8d33e08 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/27 21:24 linux-5.15.y 3330a8d33e08 2cf092b8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/25 23:07 linux-5.15.y 3330a8d33e08 e0f78d93 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/25 16:59 linux-5.15.y 3330a8d33e08 94a9671e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/23 15:03 linux-5.15.y 3330a8d33e08 6beca497 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/22 17:09 linux-5.15.y 3330a8d33e08 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/22 02:10 linux-5.15.y 3330a8d33e08 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/21 22:20 linux-5.15.y 3330a8d33e08 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/20 06:13 linux-5.15.y 3330a8d33e08 17d780d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/18 18:45 linux-5.15.y e45d5d41c134 77d4d919 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/17 22:53 linux-5.15.y e45d5d41c134 06ec4f7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/17 22:06 linux-5.15.y e45d5d41c134 06ec4f7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/16 19:42 linux-5.15.y e45d5d41c134 5d52cba5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/16 18:07 linux-5.15.y e45d5d41c134 5d52cba5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/16 05:40 linux-5.15.y e45d5d41c134 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
2026/02/15 00:32 linux-5.15.y e45d5d41c134 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_writepages
* Struck through repros no longer work on HEAD.