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: 506d, last: 1h54m
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 612 1d12h 176d 0/3 upstream: reported C repro on 2025/09/10 22:18
upstream possible deadlock in ext4_writepages ext4 4 1 1301d 1297d 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 474 4h16m 174d 0/2 upstream: reported syz repro on 2025/09/12 16:06
linux-5.15 possible deadlock in ext4_writepages 4 2 1037d 1038d 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 325 5h09m 176d 0/3 upstream: reported syz repro on 2025/09/10 19:34

Sample crash report:
loop0: detected capacity change from 0 to 512
EXT4-fs: Ignoring removed nobh option
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/6028 is trying to acquire lock:
ffff888039f10c58 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: percpu_down_read include/linux/percpu-rwsem.h:77 [inline]
ffff888039f10c58 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages_down_read fs/ext4/ext4.h:1813 [inline]
ffff888039f10c58 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_writepages+0x205/0x3b0 fs/ext4/inode.c:3018

but task is already holding lock:
ffff888058603038 (&ei->xattr_sem){++++}-{4:4}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:164 [inline]
ffff888058603038 (&ei->xattr_sem){++++}-{4:4}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:6337 [inline]
ffff888058603038 (&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:

-> #2 (&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_create+0x233/0x470 fs/ext4/namei.c:2820
       lookup_open fs/namei.c:4483 [inline]
       open_last_lookups fs/namei.c:4583 [inline]
       path_openat+0x13b4/0x38a0 fs/namei.c:4827
       do_file_open+0x23e/0x4a0 fs/namei.c:4859
       do_sys_openat2+0x113/0x200 fs/open.c:1366
       do_sys_open fs/open.c:1372 [inline]
       __do_sys_openat fs/open.c:1388 [inline]
       __se_sys_openat fs/open.c:1383 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1383
       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

-> #1 (jbd2_handle){++++}-{0:0}:
       wait_transaction_locked+0x1c2/0x280 fs/jbd2/transaction.c:151
       add_transaction_credits fs/jbd2/transaction.c:222 [inline]
       start_this_handle+0x7dc/0x2290 fs/jbd2/transaction.c:403
       jbd2__journal_start+0x2c0/0x5b0 fs/jbd2/transaction.c:501
       __ext4_journal_start_sb+0x203/0x620 fs/ext4/ext4_jbd2.c:114
       __ext4_journal_start fs/ext4/ext4_jbd2.h:242 [inline]
       ext4_do_writepages+0xf97/0x46e0 fs/ext4/inode.c:2907
       ext4_writepages+0x241/0x3b0 fs/ext4/inode.c:3019
       do_writepages+0x32e/0x550 mm/page-writeback.c:2554
       __writeback_single_inode+0x133/0x11a0 fs/fs-writeback.c:1750
       writeback_sb_inodes+0x995/0x19d0 fs/fs-writeback.c:2042
       __writeback_inodes_wb+0x111/0x240 fs/fs-writeback.c:2118
       wb_writeback+0x46a/0xb70 fs/fs-writeback.c:2229
       wb_check_old_data_flush fs/fs-writeback.c:2333 [inline]
       wb_do_writeback fs/fs-writeback.c:2386 [inline]
       wb_workfn+0xb52/0xf60 fs/fs-writeback.c:2414
       process_one_work kernel/workqueue.c:3275 [inline]
       process_scheduled_works+0xb02/0x1830 kernel/workqueue.c:3358
       worker_thread+0xa50/0xfc0 kernel/workqueue.c:3439
       kthread+0x388/0x470 kernel/kthread.c:467
       ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #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:

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

 *** DEADLOCK ***

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

stack backtrace:
CPU: 0 UID: 0 PID: 6028 Comm: syz.0.17 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:0x7f02108ada0a
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:00007ffe8f4ec078 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffe8f4ec100 RCX: 00007f02108ada0a
RDX: 0000200000000180 RSI: 0000200000000140 RDI: 00007ffe8f4ec0c0
RBP: 0000200000000180 R08: 00007ffe8f4ec100 R09: 0000000000800718
R10: 0000000000800718 R11: 0000000000000246 R12: 0000200000000140
R13: 00007ffe8f4ec0c0 R14: 00000000000004a3 R15: 00002000000003c0
 </TASK>
------------[ cut here ]------------
EA inode 11 i_nlink=1026
WARNING: fs/ext4/xattr.c:1059 at ext4_xattr_inode_update_ref+0x4c9/0x5a0 fs/ext4/xattr.c:1057, CPU#0: syz.0.17/6028
Modules linked in:
CPU: 0 UID: 0 PID: 6028 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:ext4_xattr_inode_update_ref+0x511/0x5a0 fs/ext4/xattr.c:1057
Code: 74 08 4c 89 ef e8 0f 54 9b ff 4d 8b 6d 00 48 b8 00 00 00 00 00 fc ff df 41 0f b6 04 06 84 c0 75 77 41 8b 17 4c 89 e7 4c 89 ee <67> 48 0f b9 3a 4c 8b 6c 24 28 e9 59 fe ff ff e8 bb f1 92 08 44 89
RSP: 0018:ffffc90003b2f100 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 00000000ffffffff RCX: dffffc0000000000
RDX: 0000000000000402 RSI: 000000000000000b RDI: ffffffff8f7074f0
RBP: ffffc90003b2f200 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed10089c8228 R12: ffffffff8f7074f0
R13: 000000000000000b R14: 1ffff110089c81ec R15: ffff888044e40f60
FS:  00005555605a4500(0000) GS:ffff888126340000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8ef4944000 CR3: 000000003f346000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1082 [inline]
 ext4_xattr_set_entry+0xabb/0x1e20 fs/ext4/xattr.c:1724
 ext4_xattr_ibody_set+0x254/0x6a0 fs/ext4/xattr.c:2273
 ext4_xattr_move_to_block fs/ext4/xattr.c:2676 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2744 [inline]
 ext4_expand_extra_isize_ea+0x13a2/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:0x7f02108ada0a
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:00007ffe8f4ec078 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffe8f4ec100 RCX: 00007f02108ada0a
RDX: 0000200000000180 RSI: 0000200000000140 RDI: 00007ffe8f4ec0c0
RBP: 0000200000000180 R08: 00007ffe8f4ec100 R09: 0000000000800718
R10: 0000000000800718 R11: 0000000000000246 R12: 0000200000000140
R13: 00007ffe8f4ec0c0 R14: 00000000000004a3 R15: 00002000000003c0
 </TASK>
----------------
Code disassembly (best guess):
   0:	74 08                	je     0xa
   2:	4c 89 ef             	mov    %r13,%rdi
   5:	e8 0f 54 9b ff       	call   0xff9b5419
   a:	4d 8b 6d 00          	mov    0x0(%r13),%r13
   e:	48 b8 00 00 00 00 00 	movabs $0xdffffc0000000000,%rax
  15:	fc ff df
  18:	41 0f b6 04 06       	movzbl (%r14,%rax,1),%eax
  1d:	84 c0                	test   %al,%al
  1f:	75 77                	jne    0x98
  21:	41 8b 17             	mov    (%r15),%edx
  24:	4c 89 e7             	mov    %r12,%rdi
  27:	4c 89 ee             	mov    %r13,%rsi
* 2a:	67 48 0f b9 3a       	ud1    (%edx),%rdi <-- trapping instruction
  2f:	4c 8b 6c 24 28       	mov    0x28(%rsp),%r13
  34:	e9 59 fe ff ff       	jmp    0xfffffe92
  39:	e8 bb f1 92 08       	call   0x892f1f9
  3e:	44                   	rex.R
  3f:	89                   	.byte 0x89

Crashes (4195):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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/11/21 01:05 upstream 8e621c9a3375 2cc4c24a .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/06 08:38 upstream 5ee8dbf54602 31e9c887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/06 05:15 upstream 5ee8dbf54602 31e9c887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/06 03:36 upstream 5ee8dbf54602 31e9c887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/06 02:20 upstream 5ee8dbf54602 31e9c887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/05 15:51 upstream c107785c7e8d d20b04c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/05 09:33 upstream ecc64d2dc9ff a9fe5c9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/05 02:15 upstream ecc64d2dc9ff a9fe5c9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/03/04 19:46 upstream 0031c06807cf e6b6b96b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/04 14:41 upstream 0031c06807cf e6b6b96b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/04 11:44 upstream 0031c06807cf e6b6b96b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/04 09:45 upstream 0031c06807cf 4180d919 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/04 08:07 upstream 0031c06807cf 4180d919 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/04 01:46 upstream 0031c06807cf 4180d919 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/03 23:24 upstream af4e9ef3d784 4180d919 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/03 12:45 upstream af4e9ef3d784 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/03 11:41 upstream af4e9ef3d784 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/03 09:26 upstream af4e9ef3d784 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/03 07:45 upstream af4e9ef3d784 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/02 12:44 upstream 11439c4635ed b9dd6534 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/02 11:24 upstream 11439c4635ed 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/02 10:22 upstream 11439c4635ed 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/02 09:02 upstream 11439c4635ed 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/02 07:57 upstream 11439c4635ed 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/02 05:58 upstream 11439c4635ed 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/02 00:25 upstream eb71ab2bf722 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/01 09:42 upstream 42eb01783091 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/03/01 06:54 upstream 42eb01783091 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/28 19:44 upstream 4d349ee5c778 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/28 17:53 upstream 4d349ee5c778 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/28 11:19 upstream 4d349ee5c778 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/27 18:36 upstream a75cb869a8cc 2cf092b8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/27 12:06 upstream a75cb869a8cc a2f13f71 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/27 10:59 upstream a75cb869a8cc a2f13f71 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/27 01:27 upstream f4d0ec0aa20d ffa54287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/27 01:00 upstream f4d0ec0aa20d ffa54287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/26 23:42 upstream f4d0ec0aa20d ffa54287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/26 20:04 upstream f4d0ec0aa20d ffa54287 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/26 13:04 upstream f4d0ec0aa20d ffa54287 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_writepages
2026/02/26 09:05 upstream d9d32e5bd5a4 e0f78d93 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_writepages
2026/02/26 03:40 upstream d9d32e5bd5a4 e0f78d93 .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/06 00:10 linux-next 3f9cd19e764b 31e9c887 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/03/03 21:46 linux-next c025f6cf4209 4180d919 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/03/03 14:52 linux-next d517cb8cea01 4180d919 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/03/03 10:40 linux-next d517cb8cea01 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/03/03 02:32 linux-next d517cb8cea01 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/03/03 00:53 linux-next d517cb8cea01 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/03/01 19:22 linux-next 3fa5e5702a82 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/03/01 16:26 linux-next 3fa5e5702a82 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/03/01 11:55 linux-next 3fa5e5702a82 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_writepages
2026/03/01 03:20 linux-next 3fa5e5702a82 43249bac .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.