syzbot


possible deadlock in ext4_writepages (2)

Status: upstream: reported C repro on 2024/10/19 20:27
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+eb5b4ef634a018917f3c@syzkaller.appspotmail.com
First crash: 526d, last: 18m
Cause bisection: introduced by (bisect log) [merge commit]:
commit af96134dc8562f9fcbb8358af36f6086619a29ab
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue Jun 27 17:37:01 2023 +0000

  Merge tag 'rcu.2023.06.22a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu

Crash: possible deadlock in ext4_writepages (log)
Repro: C syz .config
  
Discussions (6)
Title Replies (including bot) Last reply
[syzbot] Monthly ext4 report (Mar 2026) 0 (1) 2026/03/03 23:42
[syzbot] Monthly ext4 report (Jan 2026) 0 (1) 2026/01/30 12:35
[syzbot] Monthly ext4 report (Dec 2025) 0 (1) 2025/12/30 09:52
[syzbot] Monthly ext4 report (Nov 2025) 0 (1) 2025/11/28 21:21
[syzbot] Monthly ext4 report (Oct 2025) 0 (1) 2025/10/29 09:02
[syzbot] [ext4?] possible deadlock in ext4_writepages (2) 1 (3) 2025/09/10 00:46
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 692 9h19m 196d 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
linux-6.6 possible deadlock in ext4_writepages origin:upstream 4 syz 521 1d04h 194d 0/2 upstream: reported syz repro on 2025/09/12 16:06
linux-5.15 possible deadlock in ext4_writepages 4 2 1057d 1058d 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 C 361 10h19m 196d 0/3 upstream: reported C repro on 2025/09/10 19:34

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.30/6083 is trying to acquire lock:
ffff88803287ac58 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: percpu_down_read include/linux/percpu-rwsem.h:77 [inline]
ffff88803287ac58 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages_down_read fs/ext4/ext4.h:1813 [inline]
ffff88803287ac58 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x205/0x3b0 fs/ext4/inode.c:3018

but task is already holding lock:
ffff88805c46eb98 (&ei->xattr_sem){++++}-{4:4}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:164 [inline]
ffff88805c46eb98 (&ei->xattr_sem){++++}-{4:4}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:6337 [inline]
ffff88805c46eb98 (&ei->xattr_sem){++++}-{4:4}, at: __ext4_mark_inode_dirty+0x3db/0x730 fs/ext4/inode.c:6418

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ei->xattr_sem){++++}-{4:4}:
       down_write+0x3a/0x50 kernel/locking/rwsem.c:1590
       ext4_write_lock_xattr fs/ext4/xattr.h:157 [inline]
       ext4_xattr_set_handle+0x19c/0x14c0 fs/ext4/xattr.c:2372
       ext4_initxattrs+0x9f/0x110 fs/ext4/xattr_security.c:44
       security_inode_init_security+0x296/0x3d0 security/security.c:1344
       __ext4_new_inode+0x332f/0x3d20 fs/ext4/ialloc.c:1324
       ext4_ext_migrate+0x740/0x1140 fs/ext4/migrate.c:462
       __ext4_ioctl fs/ext4/ioctl.c:1693 [inline]
       ext4_ioctl+0x2355/0x4b40 fs/ext4/ioctl.c:1922
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:597 [inline]
       __se_sys_ioctl+0xff/0x170 fs/ioctl.c:583
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237
       lock_acquire+0xf0/0x2e0 kernel/locking/lockdep.c:5868
       percpu_down_read_internal+0x48/0x1d0 include/linux/percpu-rwsem.h:53
       percpu_down_read include/linux/percpu-rwsem.h:77 [inline]
       ext4_writepages_down_read fs/ext4/ext4.h:1813 [inline]
       ext4_writepages+0x205/0x3b0 fs/ext4/inode.c:3018
       do_writepages+0x32e/0x550 mm/page-writeback.c:2554
       __writeback_single_inode+0x133/0x11a0 fs/fs-writeback.c:1750
       writeback_single_inode+0x488/0xd60 fs/fs-writeback.c:1869
       write_inode_now+0x1c2/0x290 fs/fs-writeback.c:2954
       iput_final fs/inode.c:1956 [inline]
       iput+0x8c1/0xe80 fs/inode.c:2015
       ext4_xattr_block_set+0x1fd4/0x2ad0 fs/ext4/xattr.c:2204
       ext4_xattr_move_to_block fs/ext4/xattr.c:2669 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2744 [inline]
       ext4_expand_extra_isize_ea+0x12cf/0x1ea0 fs/ext4/xattr.c:2832
       __ext4_expand_extra_isize+0x30d/0x400 fs/ext4/inode.c:6297
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:6340 [inline]
       __ext4_mark_inode_dirty+0x45c/0x730 fs/ext4/inode.c:6418
       ext4_evict_inode+0x7a1/0xeb0 fs/ext4/inode.c:255
       evict+0x61e/0xb10 fs/inode.c:846
       ext4_orphan_cleanup+0xc38/0x1470 fs/ext4/orphan.c:472
       __ext4_fill_super fs/ext4/super.c:5668 [inline]
       ext4_fill_super+0x5a0b/0x6320 fs/ext4/super.c:5791
       get_tree_bdev_flags+0x431/0x4f0 fs/super.c:1694
       vfs_get_tree+0x92/0x2a0 fs/super.c:1754
       fc_mount fs/namespace.c:1193 [inline]
       do_new_mount_fc fs/namespace.c:3763 [inline]
       do_new_mount+0x341/0xd30 fs/namespace.c:3839
       do_mount fs/namespace.c:4172 [inline]
       __do_sys_mount fs/namespace.c:4361 [inline]
       __se_sys_mount+0x31d/0x420 fs/namespace.c:4338
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

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);
  rlock(&sbi->s_writepages_rwsem);

 *** DEADLOCK ***

3 locks held by syz.0.30/6083:
 #0: ffff88803d29a0d0 (&type->s_umount_key#28/1){+.+.}-{4:4}, at: alloc_super+0x28c/0xac0 fs/super.c:345
 #1: ffff88803d29a770 (sb_internal){.+.+}-{0:0}, at: percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline]
 #1: ffff88803d29a770 (sb_internal){.+.+}-{0:0}, at: __sb_start_write include/linux/fs/super.h:19 [inline]
 #1: ffff88803d29a770 (sb_internal){.+.+}-{0:0}, at: sb_start_intwrite include/linux/fs/super.h:177 [inline]
 #1: ffff88803d29a770 (sb_internal){.+.+}-{0:0}, at: ext4_evict_inode+0x274/0xeb0 fs/ext4/inode.c:216
 #2: ffff88805c46eb98 (&ei->xattr_sem){++++}-{4:4}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:164 [inline]
 #2: ffff88805c46eb98 (&ei->xattr_sem){++++}-{4:4}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:6337 [inline]
 #2: ffff88805c46eb98 (&ei->xattr_sem){++++}-{4:4}, at: __ext4_mark_inode_dirty+0x3db/0x730 fs/ext4/inode.c:6418

stack backtrace:
CPU: 1 UID: 0 PID: 6083 Comm: syz.0.30 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043
 check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain kernel/locking/lockdep.c:3908 [inline]
 __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0xf0/0x2e0 kernel/locking/lockdep.c:5868
 percpu_down_read_internal+0x48/0x1d0 include/linux/percpu-rwsem.h:53
 percpu_down_read include/linux/percpu-rwsem.h:77 [inline]
 ext4_writepages_down_read fs/ext4/ext4.h:1813 [inline]
 ext4_writepages+0x205/0x3b0 fs/ext4/inode.c:3018
 do_writepages+0x32e/0x550 mm/page-writeback.c:2554
 __writeback_single_inode+0x133/0x11a0 fs/fs-writeback.c:1750
 writeback_single_inode+0x488/0xd60 fs/fs-writeback.c:1869
 write_inode_now+0x1c2/0x290 fs/fs-writeback.c:2954
 iput_final fs/inode.c:1956 [inline]
 iput+0x8c1/0xe80 fs/inode.c:2015
 ext4_xattr_block_set+0x1fd4/0x2ad0 fs/ext4/xattr.c:2204
 ext4_xattr_move_to_block fs/ext4/xattr.c:2669 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2744 [inline]
 ext4_expand_extra_isize_ea+0x12cf/0x1ea0 fs/ext4/xattr.c:2832
 __ext4_expand_extra_isize+0x30d/0x400 fs/ext4/inode.c:6297
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:6340 [inline]
 __ext4_mark_inode_dirty+0x45c/0x730 fs/ext4/inode.c:6418
 ext4_evict_inode+0x7a1/0xeb0 fs/ext4/inode.c:255
 evict+0x61e/0xb10 fs/inode.c:846
 ext4_orphan_cleanup+0xc38/0x1470 fs/ext4/orphan.c:472
 __ext4_fill_super fs/ext4/super.c:5668 [inline]
 ext4_fill_super+0x5a0b/0x6320 fs/ext4/super.c:5791
 get_tree_bdev_flags+0x431/0x4f0 fs/super.c:1694
 vfs_get_tree+0x92/0x2a0 fs/super.c:1754
 fc_mount fs/namespace.c:1193 [inline]
 do_new_mount_fc fs/namespace.c:3763 [inline]
 do_new_mount+0x341/0xd30 fs/namespace.c:3839
 do_mount fs/namespace.c:4172 [inline]
 __do_sys_mount fs/namespace.c:4361 [inline]
 __se_sys_mount+0x31d/0x420 fs/namespace.c:4338
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f194e6fda0a
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:00007ffcab67c2d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffcab67c360 RCX: 00007f194e6fda0a
RDX: 0000200000000180 RSI: 0000200000000000 RDI: 00007ffcab67c320
RBP: 0000200000000180 R08: 00007ffcab67c360 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000200000000000
R13: 00007ffcab67c320 R14: 000000000000047a R15: 0000200000000b40
 </TASK>
EXT4-fs error (device loop0): ext4_xattr_inode_iget:441: inode #11: comm syz.0.30: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop0): ext4_xattr_inode_iget:446: comm syz.0.30: error while reading EA inode 11 err=-117
loop0: lost filesystem error report for type 5 error -117
EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2858: Unable to expand inode 15. Delete some EAs or run e2fsck.
EXT4-fs error (device loop0): ext4_xattr_inode_iget:441: inode #11: comm syz.0.30: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop0): ext4_xattr_inode_iget:446: comm syz.0.30: error while reading EA inode 11 err=-117
loop0: lost filesystem error report for type 5 error -117
EXT4-fs error (device loop0): ext4_xattr_inode_iget:441: inode #18: comm syz.0.30: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop0): ext4_xattr_inode_iget:446: comm syz.0.30: error while reading EA inode 18 err=-117
loop0: lost filesystem error report for type 5 error -117
EXT4-fs error (device loop0): ext4_xattr_inode_iget:441: inode #18: comm syz.0.30: iget: bad extra_isize 90 (inode size 256)
EXT4-fs error (device loop0): ext4_xattr_inode_iget:446: comm syz.0.30: error while reading EA inode 18 err=-117
loop0: lost filesystem error report for type 5 error -117
EXT4-fs (loop0): 1 orphan inode deleted
EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: writeback.
EXT4-fs (loop0): unmounting filesystem 00000000-0000-0000-0000-000000000000.

Crashes (4759):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/03/22 16:03 upstream 113ae7b4decc 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-upstream-fs possible deadlock in ext4_writepages
2026/03/04 07:00 upstream 0031c06807cf 4180d919 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2026/02/19 13:26 upstream c22e26bd0906 746545b8 .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-upstream-fs possible deadlock in ext4_writepages
2025/12/21 19:05 upstream 9094662f6707 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/19 04:30 upstream 516471569089 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/17 13:08 upstream ea1013c15392 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/04 10:23 upstream 8f7aa3d3c732 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/04 00:29 upstream 3f9f0252130e d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/03 07:58 upstream d61f1cc5db79 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/02 11:40 upstream 1d18101a644e d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/02 06:56 upstream 1d18101a644e d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/02 05:04 upstream 1d18101a644e d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/01 13:52 upstream 7d0a66e4bb90 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/01 12:44 upstream 7d0a66e4bb90 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/12/01 01:12 upstream e69c7c175115 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/30 20:10 upstream e69c7c175115 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/30 06:20 upstream 6bda50f4333f d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/30 05:42 upstream 6bda50f4333f d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/30 04:31 upstream 6bda50f4333f d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/30 03:19 upstream 6bda50f4333f d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/28 22:11 upstream e538109ac71d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/28 18:37 upstream e538109ac71d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/28 17:58 upstream e538109ac71d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/28 17:18 upstream e538109ac71d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/27 17:32 upstream 765e56e41a5a d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/27 16:41 upstream 765e56e41a5a d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/27 03:46 upstream 4941a17751c9 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/26 13:11 upstream 30f09200cc4a 64219f15 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/25 21:43 upstream 8a2bcda5e139 64219f15 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/25 20:39 upstream 8a2bcda5e139 64219f15 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/25 19:29 upstream 8a2bcda5e139 64219f15 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/25 12:49 upstream ac3fd01e4c1e 64219f15 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/24 04:38 upstream d0e88704d96c 4fb8ef37 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/24 02:47 upstream d0e88704d96c 4fb8ef37 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/24 01:22 upstream d0e88704d96c 4fb8ef37 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/23 01:25 upstream 89edd36fd801 4fb8ef37 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/23 00:40 upstream 89edd36fd801 4fb8ef37 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/22 22:29 upstream 89edd36fd801 4fb8ef37 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/22 14:15 upstream 2eba5e05d9bc 4fb8ef37 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/11/21 13:46 upstream fd95357fd8c6 280ea308 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/09/10 11:50 upstream 9dd1835ecda5 fdeaa69b .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/09/09 23:28 upstream 9dd1835ecda5 d291dd2d .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2025/10/30 19:30 upstream e53642b87a4f 2c50b6a9 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root possible deadlock in ext4_writepages
2026/03/26 12:26 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/26 11:03 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/26 10:03 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/26 08:55 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/26 07:41 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/26 06:38 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/26 04:57 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/26 03:54 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/26 02:49 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/26 00:26 upstream d2a43e7f89da c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 23:17 upstream bbeb83d3182a 4367a094 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/25 21:45 upstream bbeb83d3182a c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 19:45 upstream bbeb83d3182a 8ee77f7d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 17:48 upstream bbeb83d3182a 4367a094 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/25 15:47 upstream bbeb83d3182a 8ee77f7d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 15:24 upstream bbeb83d3182a 8ee77f7d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 14:19 upstream bbeb83d3182a 8ee77f7d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 12:17 upstream bbeb83d3182a 8ee77f7d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 11:02 upstream bbeb83d3182a 8ee77f7d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 09:36 upstream e3c33bc767b5 35e4ff71 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/25 08:14 upstream bbeb83d3182a 8ee77f7d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 06:25 upstream e3c33bc767b5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 05:24 upstream e3c33bc767b5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 01:31 upstream e3c33bc767b5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/25 00:47 upstream e3c33bc767b5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 23:43 upstream e3c33bc767b5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 22:11 upstream e3c33bc767b5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 21:10 upstream e3c33bc767b5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 19:02 upstream e3c33bc767b5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 16:04 upstream c369299895a5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/24 15:40 upstream c369299895a5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 14:07 upstream c369299895a5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/24 12:40 upstream c369299895a5 74e70d19 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 11:19 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 10:24 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/24 09:22 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 08:03 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 06:58 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 05:53 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 05:28 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 03:35 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 02:28 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/24 01:45 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/23 23:49 upstream c369299895a5 4933dba2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/23 22:06 upstream c369299895a5 4933dba2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2024/10/15 20:23 upstream 2f87d0916ce0 7eb57b4a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/23 11:36 linux-next 785f0eb2f85d 5e3db351 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/02/09 03:26 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 59e4d31a0470 4c131dc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
* Struck through repros no longer work on HEAD.