possible deadlock in ext4_xattr_set_entry

Status: upstream: reported C repro on 2025/02/15 09:05
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+aee2d0876b688d945095@syzkaller.appspotmail.com
First crash: 550d, last: 3d11h
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2025/03/18 upstream (ToT) 81e4f8d68c66 C [report] possible deadlock in ext4_xattr_inode_lookup_create
Last patch testing requests (10)
Created Duration User Patch Repo Result
2026/07/04 01:22 16m retest repro linux-5.15.y report log
2026/07/04 01:22 15m retest repro linux-5.15.y report log
2026/07/04 01:22 30m retest repro linux-5.15.y report log
2026/06/14 08:32 15m retest repro linux-5.15.y report log
2026/06/14 08:32 15m retest repro linux-5.15.y report log
2026/06/14 08:32 15m retest repro linux-5.15.y report log
2026/04/22 14:44 16m retest repro linux-5.15.y report log
2026/04/22 14:44 16m retest repro linux-5.15.y report log
2026/04/22 08:44 23m retest repro linux-5.15.y report log
2026/04/01 17:21 10m retest repro linux-5.15.y report log
Fix bisection attempts (4)
Created Duration User Patch Repo Result
2026/03/13 10:59 5m bisect fix linux-5.15.y error job log
2026/01/04 22:17 1h04m bisect fix linux-5.15.y OK (0) job log log
2025/11/01 09:44 1h26m bisect fix linux-5.15.y OK (0) job log log
2025/04/17 07:07 1h16m bisect fix linux-5.15.y OK (0) job log log

Sample crash report:
EXT4-fs (loop0): 1 truncate cleaned up
EXT4-fs (loop0): mounted filesystem without journal. Opts: lazytime,jqfmt=vfsold,debug_want_extra_isize=0x000000000000006a,user_xattr,errors=remount-ro,nombcache,. Quota mode: none.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.73/4462 is trying to acquire lock:
ffff888060ca8de8 (&sb->s_type->i_mutex_key#9/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
ffff888060ca8de8 (&sb->s_type->i_mutex_key#9/1){+.+.}-{3:3}, at: ext4_xattr_inode_create fs/ext4/xattr.c:1465 [inline]
ffff888060ca8de8 (&sb->s_type->i_mutex_key#9/1){+.+.}-{3:3}, at: ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1547 [inline]
ffff888060ca8de8 (&sb->s_type->i_mutex_key#9/1){+.+.}-{3:3}, at: ext4_xattr_set_entry+0x3729/0x3f70 fs/ext4/xattr.c:1675

but task is already holding lock:
ffff888060ca9668 (&ei->i_data_sem/3){++++}-{3:3}, at: ext4_map_blocks+0x8c4/0x1a50 fs/ext4/inode.c:668

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ei->i_data_sem/3){++++}-{3:3}:
       down_write+0x38/0x60 kernel/locking/rwsem.c:1551
       ext4_update_i_disksize fs/ext4/ext4.h:3425 [inline]
       ext4_xattr_inode_write fs/ext4/xattr.c:1403 [inline]
       ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1551 [inline]
       ext4_xattr_set_entry+0x34ba/0x3f70 fs/ext4/xattr.c:1675
       ext4_xattr_ibody_set+0x113/0x330 fs/ext4/xattr.c:2240
       ext4_xattr_set_handle+0xa68/0x12b0 fs/ext4/xattr.c:2397
       ext4_xattr_set+0x22e/0x310 fs/ext4/xattr.c:2510
       __vfs_setxattr+0x3d8/0x410 fs/xattr.c:182
       __vfs_setxattr_noperm+0x126/0x5e0 fs/xattr.c:216
       vfs_setxattr+0x167/0x2e0 fs/xattr.c:303
       do_setxattr fs/xattr.c:588 [inline]
       setxattr+0x2cb/0x360 fs/xattr.c:611
       path_setxattr+0x147/0x290 fs/xattr.c:630
       __do_sys_setxattr fs/xattr.c:646 [inline]
       __se_sys_setxattr fs/xattr.c:642 [inline]
       __x64_sys_setxattr+0xb7/0xd0 fs/xattr.c:642
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (&sb->s_type->i_mutex_key#9/1){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
       lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
       down_write+0x38/0x60 kernel/locking/rwsem.c:1551
       inode_lock include/linux/fs.h:787 [inline]
       ext4_xattr_inode_create fs/ext4/xattr.c:1465 [inline]
       ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1547 [inline]
       ext4_xattr_set_entry+0x3729/0x3f70 fs/ext4/xattr.c:1675
       ext4_xattr_block_set+0x4d7/0x2ce0 fs/ext4/xattr.c:1926
       ext4_xattr_move_to_block fs/ext4/xattr.c:2620 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2695 [inline]
       ext4_expand_extra_isize_ea+0xebe/0x18e0 fs/ext4/xattr.c:2783
       __ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:5924
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:5967 [inline]
       __ext4_mark_inode_dirty+0x444/0x6c0 fs/ext4/inode.c:6045
       ext4_dirty_inode+0xbf/0x100 fs/ext4/inode.c:6077
       __mark_inode_dirty+0x2c8/0xc90 fs/fs-writeback.c:2480
       mark_inode_dirty include/linux/fs.h:2468 [inline]
       dquot_alloc_space include/linux/quotaops.h:310 [inline]
       dquot_alloc_block include/linux/quotaops.h:327 [inline]
       ext4_mb_new_blocks+0x2c0c/0x47c0 fs/ext4/mballoc.c:5750
       ext4_alloc_branch fs/ext4/indirect.c:340 [inline]
       ext4_ind_map_blocks+0xf0a/0x2250 fs/ext4/indirect.c:635
       ext4_map_blocks+0x929/0x1a50 fs/ext4/inode.c:677
       _ext4_get_block+0x1e7/0x540 fs/ext4/inode.c:818
       ext4_block_write_begin+0x5ff/0x1200 fs/ext4/inode.c:1103
       ext4_write_begin+0x6c8/0x15d0 fs/ext4/ext4_jbd2.h:-1
       generic_perform_write+0x2b6/0x550 mm/filemap.c:3785
       ext4_buffered_write_iter+0x24e/0x3a0 fs/ext4/file.c:268
       ext4_file_write_iter+0x73f/0x1720 fs/ext4/file.c:-1
       call_write_iter include/linux/fs.h:2173 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0x748/0xd70 fs/read_write.c:594
       ksys_write+0x153/0x260 fs/read_write.c:647
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ei->i_data_sem/3);
                               lock(&sb->s_type->i_mutex_key#9/1);
                               lock(&ei->i_data_sem/3);
  lock(&sb->s_type->i_mutex_key#9/1);

 *** DEADLOCK ***

4 locks held by syz.0.73/4462:
 #0: ffff8880760aa460 (sb_writers#5){.+.+}-{0:0}, at: vfs_write+0x296/0xd70 fs/read_write.c:590
 #1: ffff888060ca97e0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff888060ca97e0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa1/0x3a0 fs/ext4/file.c:262
 #2: ffff888060ca9668 (&ei->i_data_sem/3){++++}-{3:3}, at: ext4_map_blocks+0x8c4/0x1a50 fs/ext4/inode.c:668
 #3: ffff888060ca94b8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:165 [inline]
 #3: ffff888060ca94b8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:5964 [inline]
 #3: ffff888060ca94b8 (&ei->xattr_sem){++++}-{3:3}, at: __ext4_mark_inode_dirty+0x3bd/0x6c0 fs/ext4/inode.c:6045

stack backtrace:
CPU: 0 PID: 4462 Comm: syz.0.73 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 down_write+0x38/0x60 kernel/locking/rwsem.c:1551
 inode_lock include/linux/fs.h:787 [inline]
 ext4_xattr_inode_create fs/ext4/xattr.c:1465 [inline]
 ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1547 [inline]
 ext4_xattr_set_entry+0x3729/0x3f70 fs/ext4/xattr.c:1675
 ext4_xattr_block_set+0x4d7/0x2ce0 fs/ext4/xattr.c:1926
 ext4_xattr_move_to_block fs/ext4/xattr.c:2620 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2695 [inline]
 ext4_expand_extra_isize_ea+0xebe/0x18e0 fs/ext4/xattr.c:2783
 __ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:5924
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5967 [inline]
 __ext4_mark_inode_dirty+0x444/0x6c0 fs/ext4/inode.c:6045
 ext4_dirty_inode+0xbf/0x100 fs/ext4/inode.c:6077
 __mark_inode_dirty+0x2c8/0xc90 fs/fs-writeback.c:2480
 mark_inode_dirty include/linux/fs.h:2468 [inline]
 dquot_alloc_space include/linux/quotaops.h:310 [inline]
 dquot_alloc_block include/linux/quotaops.h:327 [inline]
 ext4_mb_new_blocks+0x2c0c/0x47c0 fs/ext4/mballoc.c:5750
 ext4_alloc_branch fs/ext4/indirect.c:340 [inline]
 ext4_ind_map_blocks+0xf0a/0x2250 fs/ext4/indirect.c:635
 ext4_map_blocks+0x929/0x1a50 fs/ext4/inode.c:677
 _ext4_get_block+0x1e7/0x540 fs/ext4/inode.c:818
 ext4_block_write_begin+0x5ff/0x1200 fs/ext4/inode.c:1103
 ext4_write_begin+0x6c8/0x15d0 fs/ext4/ext4_jbd2.h:-1
 generic_perform_write+0x2b6/0x550 mm/filemap.c:3785
 ext4_buffered_write_iter+0x24e/0x3a0 fs/ext4/file.c:268
 ext4_file_write_iter+0x73f/0x1720 fs/ext4/file.c:-1
 call_write_iter include/linux/fs.h:2173 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0x748/0xd70 fs/read_write.c:594
 ksys_write+0x153/0x260 fs/read_write.c:647
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8e0a0610d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 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:00007ffce662bfa8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f8e0a2e8fa0 RCX: 00007f8e0a0610d9
RDX: 0000000000002400 RSI: 0000200000000000 RDI: 0000000000000004
RBP: 00007f8e0a0f8024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8e0a2e8fac R14: 00007f8e0a2e8fa0 R15: 00007f8e0a2e8fa0
 </TASK>

Crashes (181):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/16 02:20 linux-5.15.y aabd761612db 746171ee .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/08/15 21:20 linux-5.15.y aabd761612db 746171ee .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/04/28 07:05 linux-5.15.y b9d57c40a767 ce741359 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/11/13 04:31 linux-5.15.y cc5ec8769306 07e030de .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/06/04 08:07 linux-5.15.y 98f47d0e9b8c a30356b7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/02/15 16:38 linux-5.15.y c16c81c81336 40a34ec9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/06/15 16:01 linux-5.15.y 1c700860e8bc 5f4b362d .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan-arm64 possible deadlock in ext4_xattr_set_entry
2025/02/15 15:14 linux-5.15.y c16c81c81336 40a34ec9 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/08/15 20:13 linux-5.15.y aabd761612db 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/06/15 08:37 linux-5.15.y dc027a595035 1d2f3589 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/05/30 21:43 linux-5.15.y 241d66fa280c 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/05/15 22:53 linux-5.15.y 93741761e5e3 81fb92f3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/05/08 02:45 linux-5.15.y ef251c45f1cd 5633175a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/05/03 13:31 linux-5.15.y ef251c45f1cd a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/04/30 13:43 linux-5.15.y ef251c45f1cd a7464baf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/04/29 22:59 linux-5.15.y b9d57c40a767 005438fc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/04/29 10:51 linux-5.15.y b9d57c40a767 7ca9e4d8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2026/04/27 23:33 linux-5.15.y b9d57c40a767 ce741359 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/11/18 02:32 linux-5.15.y cc5ec8769306 ef766cd7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/11/17 12:58 linux-5.15.y cc5ec8769306 ef766cd7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/11/16 09:06 linux-5.15.y cc5ec8769306 f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/11/12 14:10 linux-5.15.y cc5ec8769306 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/18 09:37 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/12 01:39 linux-5.15.y c79648372d02 c06e8995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/10 07:25 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/10 06:14 linux-5.15.y c79648372d02 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/08 04:21 linux-5.15.y c79648372d02 6a893178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/06 01:24 linux-5.15.y c79648372d02 ffe1dd46 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/05 12:25 linux-5.15.y c79648372d02 37880f40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/03 15:02 linux-5.15.y c79648372d02 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/02 10:12 linux-5.15.y c79648372d02 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/02 10:09 linux-5.15.y c79648372d02 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/02 05:31 linux-5.15.y c79648372d02 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/02 05:01 linux-5.15.y c79648372d02 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/02 03:52 linux-5.15.y c79648372d02 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/01 23:17 linux-5.15.y c79648372d02 40127d41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/08/01 23:11 linux-5.15.y c79648372d02 40127d41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/07/30 11:17 linux-5.15.y c79648372d02 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/07/30 05:19 linux-5.15.y c79648372d02 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/07/30 00:20 linux-5.15.y c79648372d02 f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/07/28 18:51 linux-5.15.y c79648372d02 6654ea9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/07/27 18:20 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/07/25 19:46 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/07/25 13:06 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/07/24 14:22 linux-5.15.y c79648372d02 65d60d73 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/02/15 09:05 linux-5.15.y c16c81c81336 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_set_entry
2025/07/25 10:40 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ext4_xattr_set_entry
2025/07/25 10:26 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ext4_xattr_set_entry
2025/07/25 08:59 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ext4_xattr_set_entry
2025/07/25 06:31 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ext4_xattr_set_entry
* Struck through repros no longer work on HEAD.