possible deadlock in ext4_writepages (2)

Status: upstream: reported C repro on 2024/10/19 20:27
Subsystems: ext4
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+eb5b4ef634a018917f3c@syzkaller.appspotmail.com
First crash: 693d, last: 5d14h
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
  
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision
3552fa69 assessment-security DenialOfService: ❌ Exploitable: ❌ FilesystemTrigger: ✅ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ possible deadlock in ext4_writepages (2) 2026/06/01 07:43 2026/06/01 07:43 2026/06/01 08:20 6b4a8443
f1f24df9 assessment-security 💥 possible deadlock in ext4_writepages (2) 2026/05/15 10:37 2026/05/15 10:37 2026/05/15 10:38 9cd3beaa
Discussions (11)
Title Replies (including bot) Last reply
[syzbot] Monthly ext4 report (Aug 2026) 0 (1) 2026/08/11 04:32
[syzbot] Monthly ext4 report (Jul 2026) 0 (1) 2026/07/10 20:32
[syzbot] Monthly ext4 report (Jun 2026) 0 (1) 2026/06/09 20:32
[syzbot] Monthly ext4 report (May 2026) 0 (1) 2026/05/09 12:32
[syzbot] Monthly ext4 report (Apr 2026) 0 (1) 2026/04/08 06:44
[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 syz, C 1242 1d09h 363d 0/3 upstream: reported C repro on 2025/09/10 22:18
upstream possible deadlock in ext4_writepages ext4 4 1 1487d 1483d 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, C 757 9d22h 361d 0/2 upstream: reported C repro on 2025/09/12 16:06
linux-5.15 possible deadlock in ext4_writepages 4 2 1223d 1225d 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, C 673 1d16h 363d 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-executor184/5657 is trying to acquire lock:
ffff888025f9ccd8 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: percpu_down_read include/linux/percpu-rwsem.h:77 [inline]
ffff888025f9ccd8 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages_down_read fs/ext4/ext4.h:1876 [inline]
ffff888025f9ccd8 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x205/0x3b0 fs/ext4/inode.c:3042

but task is already holding lock:
ffff888044d16b50 (&ei->xattr_sem){++++}-{4:4}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:164 [inline]
ffff888044d16b50 (&ei->xattr_sem){++++}-{4:4}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:6526 [inline]
ffff888044d16b50 (&ei->xattr_sem){++++}-{4:4}, at: __ext4_mark_inode_dirty+0x3d0/0x700 fs/ext4/inode.c:6607

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:1631
       ext4_write_lock_xattr fs/ext4/xattr.h:157 [inline]
       ext4_xattr_set_handle+0x194/0x1540 fs/ext4/xattr.c:2374
       ext4_initxattrs+0xa4/0x120 fs/ext4/xattr_security.c:44
       security_inode_init_security+0x29b/0x3e0 security/security.c:1370
       __ext4_new_inode+0x3435/0x3e40 fs/ext4/ialloc.c:1332
       ext4_ext_migrate+0x718/0x10e0 fs/ext4/migrate.c:462
       __ext4_ioctl fs/ext4/ioctl.c:1702 [inline]
       ext4_ioctl+0x234f/0x4b80 fs/ext4/ioctl.c:1931
       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+0x174/0x580 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+0x1520/0x2ce0 kernel/locking/lockdep.c:5237
       lock_acquire+0x106/0x350 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:1876 [inline]
       ext4_writepages+0x205/0x3b0 fs/ext4/inode.c:3042
       do_writepages+0x338/0x560 mm/page-writeback.c:2571
       __writeback_single_inode+0x12e/0xf90 fs/fs-writeback.c:1787
       writeback_single_inode+0x4dd/0xe10 fs/fs-writeback.c:1906
       write_inode_now+0x1c2/0x290 fs/fs-writeback.c:3060
       iput_final fs/inode.c:2009 [inline]
       iput+0x98b/0xf00 fs/inode.c:2068
       ext4_xattr_block_set+0x1b0c/0x2a80 fs/ext4/xattr.c:2206
       ext4_xattr_move_to_block fs/ext4/xattr.c:2671 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2746 [inline]
       ext4_expand_extra_isize_ea+0x1342/0x1e70 fs/ext4/xattr.c:2834
       __ext4_expand_extra_isize+0x30d/0x400 fs/ext4/inode.c:6486
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:6529 [inline]
       __ext4_mark_inode_dirty+0x455/0x700 fs/ext4/inode.c:6607
       ext4_evict_inode+0x976/0x10c0 fs/ext4/inode.c:267
       evict+0x624/0xb50 fs/inode.c:825
       ext4_orphan_cleanup+0xc7a/0x14c0 fs/ext4/orphan.c:472
       __ext4_fill_super fs/ext4/super.c:5705 [inline]
       ext4_fill_super+0x5cc0/0x65d0 fs/ext4/super.c:5828
       get_tree_bdev_flags+0x430/0x4f0 fs/super.c:1640
       vfs_get_tree+0x92/0x2a0 fs/super.c:1700
       fc_mount fs/namespace.c:1198 [inline]
       do_new_mount_fc fs/namespace.c:3765 [inline]
       do_new_mount+0x319/0xdc0 fs/namespace.c:3841
       do_mount fs/namespace.c:4174 [inline]
       __do_sys_mount fs/namespace.c:4390 [inline]
       __se_sys_mount+0x31d/0x420 fs/namespace.c:4367
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 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-executor184/5657:
 #0: ffff88803b8160d0 (&type->s_umount_key#29/1){+.+.}-{4:4}, at: alloc_super fs/super.c:345 [inline]
 #0: ffff88803b8160d0 (&type->s_umount_key#29/1){+.+.}-{4:4}, at: sget_fc+0x938/0x1910 fs/super.c:766
 #1: ffff88803b8167f0 (sb_internal){.+.+}-{0:0}, at: percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline]
 #1: ffff88803b8167f0 (sb_internal){.+.+}-{0:0}, at: __sb_start_write include/linux/fs/super.h:19 [inline]
 #1: ffff88803b8167f0 (sb_internal){.+.+}-{0:0}, at: sb_start_intwrite include/linux/fs/super.h:177 [inline]
 #1: ffff88803b8167f0 (sb_internal){.+.+}-{0:0}, at: ext4_evict_inode+0x426/0x10c0 fs/ext4/inode.c:228
 #2: ffff888044d16b50 (&ei->xattr_sem){++++}-{4:4}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:164 [inline]
 #2: ffff888044d16b50 (&ei->xattr_sem){++++}-{4:4}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:6526 [inline]
 #2: ffff888044d16b50 (&ei->xattr_sem){++++}-{4:4}, at: __ext4_mark_inode_dirty+0x3d0/0x700 fs/ext4/inode.c:6607

stack backtrace:
CPU: 1 UID: 0 PID: 5657 Comm: syz-executor184 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/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+0x1520/0x2ce0 kernel/locking/lockdep.c:5237
 lock_acquire+0x106/0x350 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:1876 [inline]
 ext4_writepages+0x205/0x3b0 fs/ext4/inode.c:3042
 do_writepages+0x338/0x560 mm/page-writeback.c:2571
 __writeback_single_inode+0x12e/0xf90 fs/fs-writeback.c:1787
 writeback_single_inode+0x4dd/0xe10 fs/fs-writeback.c:1906
 write_inode_now+0x1c2/0x290 fs/fs-writeback.c:3060
 iput_final fs/inode.c:2009 [inline]
 iput+0x98b/0xf00 fs/inode.c:2068
 ext4_xattr_block_set+0x1b0c/0x2a80 fs/ext4/xattr.c:2206
 ext4_xattr_move_to_block fs/ext4/xattr.c:2671 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2746 [inline]
 ext4_expand_extra_isize_ea+0x1342/0x1e70 fs/ext4/xattr.c:2834
 __ext4_expand_extra_isize+0x30d/0x400 fs/ext4/inode.c:6486
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:6529 [inline]
 __ext4_mark_inode_dirty+0x455/0x700 fs/ext4/inode.c:6607
 ext4_evict_inode+0x976/0x10c0 fs/ext4/inode.c:267
 evict+0x624/0xb50 fs/inode.c:825
 ext4_orphan_cleanup+0xc7a/0x14c0 fs/ext4/orphan.c:472
 __ext4_fill_super fs/ext4/super.c:5705 [inline]
 ext4_fill_super+0x5cc0/0x65d0 fs/ext4/super.c:5828
 get_tree_bdev_flags+0x430/0x4f0 fs/super.c:1640
 vfs_get_tree+0x92/0x2a0 fs/super.c:1700
 fc_mount fs/namespace.c:1198 [inline]
 do_new_mount_fc fs/namespace.c:3765 [inline]
 do_new_mount+0x319/0xdc0 fs/namespace.c:3841
 do_mount fs/namespace.c:4174 [inline]
 __do_sys_mount fs/namespace.c:4390 [inline]
 __se_sys_mount+0x31d/0x420 fs/namespace.c:4367
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb8602308aa
Code: 48 c7 c2 d8 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 d8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd99830a38 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffd99830a90 RCX: 00007fb8602308aa
RDX: 0000200000000240 RSI: 0000200000000000 RDI: 00007ffd99830a90
RBP: 0000200000000000 R08: 00007ffd99830ad0 R09: 00007ffd99830ad0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000200000000240
R13: 00007ffd99830ad0 R14: 000000000000047a R15: 000000000000002c
 </TASK>
EXT4-fs error (device loop0): ext4_xattr_inode_iget:441: inode #11: comm syz-executor184: iget: bad extra_isize 90 (inode size 256)
loop0: lost file I/O error report for ino 11 type 5 pos 0x0 len 0x0 error -117
EXT4-fs (loop0): Remounting filesystem read-only
EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2860: Unable to expand inode 15. Delete some EAs or run e2fsck.
EXT4-fs warning (device loop0): ext4_evict_inode:270: couldn't mark inode dirty (err -30)
EXT4-fs (loop0): 1 orphan inode deleted
EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none.
EXT4-fs (loop0): unmounting filesystem 00000000-0000-0000-0000-000000000000.

Crashes (21100):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/12 14:31 upstream f5bbbfec59b4 f8d35649 .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/05/04 23:57 upstream c7e4e4d5f7dc a898ba9c .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/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/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
2026/08/09 19:11 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ba5cc80fd326 5d63f80b .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1 (clean fs)] [mounted in repro #2 (corrupt fs)] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/07/12 14:47 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a52d6c7160f7 d78ea535 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1 (clean fs)] [mounted in repro #2 (corrupt fs)] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/07/27 06:25 upstream 4235cb24ec1e 492bab15 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1 (corrupt fs)] [mounted in repro #2 (clean fs)] ci2-upstream-fs possible deadlock in ext4_writepages
2026/07/12 14:41 upstream 44696aa3a489 d78ea535 .config console log report syz / log [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
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/08/21 01:31 upstream a4ff2be345d0 1e72964b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/08/15 02:14 upstream dac3e89a2c90 746171ee .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/07/18 03:46 linux-next cc2b5f627e8c 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/09/03 12:23 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 6a988719 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 11:13 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 6a988719 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 10:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 6a988719 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 09:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 6a988719 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 08:45 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 6a988719 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 07:34 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 6a988719 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 06:26 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 6a988719 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 04:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 03:41 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 02:58 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 01:56 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/03 00:56 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 23:44 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 23:23 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 21:39 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 20:39 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 20:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 19:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 17:54 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 16:50 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 16:24 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 14:20 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 85995287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 12:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 10:57 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 09:55 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 08:53 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 07:47 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 07:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 05:49 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 04:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 03:08 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 03:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 01:38 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/02 00:29 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 22:44 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 21:33 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 20:06 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 587f6b29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 17:45 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 16:35 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 15:28 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 15:00 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 13:50 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 11:54 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 11:05 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_writepages
2026/09/01 10:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1b8fa82cab7 316d9396 .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.