syzbot


possible deadlock in ext4_xattr_inode_lookup_create

Status: upstream: reported C repro on 2024/09/28 07:43
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+d91a6e2efb07bd3354e9@syzkaller.appspotmail.com
First crash: 259d, last: 11d
Cause bisection: introduced by (bisect log) :
commit 1e9d62d252812575ded7c620d8fc67c32ff06c16
Author: Jun Nie <jun.nie@linaro.org>
Date: Tue Jan 3 01:45:16 2023 +0000

  ext4: optimize ea_inode block expansion

Crash: possible deadlock in ext4_xattr_inode_iget (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ext4?] possible deadlock in ext4_xattr_inode_lookup_create 0 (1) 2024/09/28 07:43
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in ext4_xattr_inode_lookup_create origin:upstream C 33 1d10h 217d 0/3 upstream: reported C repro on 2024/11/04 12:41
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/05/29 22:27 20m retest repro upstream OK log
2025/05/29 22:27 14m retest repro upstream report log
2025/05/29 22:11 17m retest repro linux-next report log
2025/04/17 17:18 14m retest repro upstream report log
2025/04/17 17:18 14m retest repro upstream report log
2025/04/17 17:18 14m retest repro upstream report log
2025/03/02 11:52 30m retest repro upstream report log
2025/03/02 11:57 19m retest repro upstream report log
2025/03/02 11:39 23m retest repro upstream report log
2025/01/08 03:00 16m retest repro linux-next report log

Sample crash report:
EXT4-fs (loop0): 1 truncate cleaned up
EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: writeback.
======================================================
WARNING: possible circular locking dependency detected
6.14.0-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor670/5329 is trying to acquire lock:
ffff88804567a1b0 (&sb->s_type->i_mutex_key#8/1){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:877 [inline]
ffff88804567a1b0 (&sb->s_type->i_mutex_key#8/1){+.+.}-{4:4}, at: ext4_xattr_inode_create fs/ext4/xattr.c:1514 [inline]
ffff88804567a1b0 (&sb->s_type->i_mutex_key#8/1){+.+.}-{4:4}, at: ext4_xattr_inode_lookup_create+0x17de/0x1c70 fs/ext4/xattr.c:1596

but task is already holding lock:
ffff8880456551c8 (&ei->i_data_sem/3){++++}-{4:4}, at: ext4_setattr+0x16e1/0x1da0 fs/ext4/inode.c:5505

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ei->i_data_sem/3){++++}-{4:4}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851
       down_write+0x99/0x220 kernel/locking/rwsem.c:1577
       ext4_update_i_disksize fs/ext4/ext4.h:3375 [inline]
       ext4_xattr_inode_write fs/ext4/xattr.c:1452 [inline]
       ext4_xattr_inode_lookup_create+0x1484/0x1c70 fs/ext4/xattr.c:1602
       ext4_xattr_ibody_set+0x214/0x730 fs/ext4/xattr.c:2269
       ext4_xattr_set_handle+0xba6/0x1580 fs/ext4/xattr.c:2446
       ext4_xattr_set+0x280/0x3e0 fs/ext4/xattr.c:2560
       __vfs_setxattr+0x468/0x4a0 fs/xattr.c:200
       __vfs_setxattr_noperm+0x12e/0x660 fs/xattr.c:234
       vfs_setxattr+0x221/0x430 fs/xattr.c:321
       do_setxattr fs/xattr.c:636 [inline]
       filename_setxattr+0x2af/0x430 fs/xattr.c:665
       path_setxattrat+0x440/0x510 fs/xattr.c:713
       __do_sys_lsetxattr fs/xattr.c:754 [inline]
       __se_sys_lsetxattr fs/xattr.c:750 [inline]
       __x64_sys_lsetxattr+0xbf/0xe0 fs/xattr.c:750
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&sb->s_type->i_mutex_key#8/1){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3163 [inline]
       check_prevs_add kernel/locking/lockdep.c:3282 [inline]
       validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3906
       __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5228
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851
       down_write+0x99/0x220 kernel/locking/rwsem.c:1577
       inode_lock include/linux/fs.h:877 [inline]
       ext4_xattr_inode_create fs/ext4/xattr.c:1514 [inline]
       ext4_xattr_inode_lookup_create+0x17de/0x1c70 fs/ext4/xattr.c:1596
       ext4_xattr_block_set+0x26c/0x32d0 fs/ext4/xattr.c:1916
       ext4_xattr_move_to_block fs/ext4/xattr.c:2670 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2745 [inline]
       ext4_expand_extra_isize_ea+0x1182/0x1cf0 fs/ext4/xattr.c:2837
       __ext4_expand_extra_isize+0x306/0x400 fs/ext4/inode.c:5889
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:5932 [inline]
       __ext4_mark_inode_dirty+0x524/0x880 fs/ext4/inode.c:6010
       ext4_setattr+0x1780/0x1da0 fs/ext4/inode.c:5508
       notify_change+0xbca/0xe90 fs/attr.c:552
       do_truncate+0x220/0x310 fs/open.c:65
       handle_truncate fs/namei.c:3451 [inline]
       do_open fs/namei.c:3834 [inline]
       path_openat+0x2e1b/0x3590 fs/namei.c:3989
       do_filp_open+0x27f/0x4e0 fs/namei.c:4016
       do_sys_openat2+0x13e/0x1d0 fs/open.c:1428
       do_sys_open fs/open.c:1443 [inline]
       __do_sys_creat fs/open.c:1521 [inline]
       __se_sys_creat fs/open.c:1515 [inline]
       __x64_sys_creat+0x123/0x170 fs/open.c:1515
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

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#8/1);
                               lock(&ei->i_data_sem/3);
  lock(&sb->s_type->i_mutex_key#8/1);

 *** DEADLOCK ***

5 locks held by syz-executor670/5329:
 #0: ffff8880425c8420 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:547
 #1: ffff888045655338 (&sb->s_type->i_mutex_key#8){++++}-{4:4}, at: inode_lock include/linux/fs.h:877 [inline]
 #1: ffff888045655338 (&sb->s_type->i_mutex_key#8){++++}-{4:4}, at: do_truncate+0x20c/0x310 fs/open.c:63
 #2: ffff8880456554d8 (mapping.invalidate_lock){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:922 [inline]
 #2: ffff8880456554d8 (mapping.invalidate_lock){++++}-{4:4}, at: ext4_setattr+0xf94/0x1da0 fs/ext4/inode.c:5453
 #3: ffff8880456551c8 (&ei->i_data_sem/3){++++}-{4:4}, at: ext4_setattr+0x16e1/0x1da0 fs/ext4/inode.c:5505
 #4: ffff888045655008 (&ei->xattr_sem){++++}-{4:4}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:161 [inline]
 #4: ffff888045655008 (&ei->xattr_sem){++++}-{4:4}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:5929 [inline]
 #4: ffff888045655008 (&ei->xattr_sem){++++}-{4:4}, at: __ext4_mark_inode_dirty+0x491/0x880 fs/ext4/inode.c:6010

stack backtrace:
CPU: 0 UID: 0 PID: 5329 Comm: syz-executor670 Not tainted 6.14.0-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2076
 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2208
 check_prev_add kernel/locking/lockdep.c:3163 [inline]
 check_prevs_add kernel/locking/lockdep.c:3282 [inline]
 validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3906
 __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5228
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851
 down_write+0x99/0x220 kernel/locking/rwsem.c:1577
 inode_lock include/linux/fs.h:877 [inline]
 ext4_xattr_inode_create fs/ext4/xattr.c:1514 [inline]
 ext4_xattr_inode_lookup_create+0x17de/0x1c70 fs/ext4/xattr.c:1596
 ext4_xattr_block_set+0x26c/0x32d0 fs/ext4/xattr.c:1916
 ext4_xattr_move_to_block fs/ext4/xattr.c:2670 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2745 [inline]
 ext4_expand_extra_isize_ea+0x1182/0x1cf0 fs/ext4/xattr.c:2837
 __ext4_expand_extra_isize+0x306/0x400 fs/ext4/inode.c:5889
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5932 [inline]
 __ext4_mark_inode_dirty+0x524/0x880 fs/ext4/inode.c:6010
 ext4_setattr+0x1780/0x1da0 fs/ext4/inode.c:5508
 notify_change+0xbca/0xe90 fs/attr.c:552
 do_truncate+0x220/0x310 fs/open.c:65
 handle_truncate fs/namei.c:3451 [inline]
 do_open fs/namei.c:3834 [inline]
 path_openat+0x2e1b/0x3590 fs/namei.c:3989
 do_filp_open+0x27f/0x4e0 fs/namei.c:4016
 do_sys_openat2+0x13e/0x1d0 fs/open.c:1428
 do_sys_open fs/open.c:1443 [inline]
 __do_sys_creat fs/open.c:1521 [inline]
 __se_sys_creat fs/open.c:1515 [inline]
 __x64_sys_creat+0x123/0x170 fs/open.c:1515
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb7da2182e9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd09100f88 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007fb7da2182e9
RDX: 00007fb7da2182e9 RSI: 00000000000001ad RDI: 0000200000000300
RBP: 0000000000000000 R08: 00007ffd09100fc0 R09: 00007ffd09100fc0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd09100fac
R13: 0000000000000008 R14: 431bde82d7b634db R15: 00007ffd09100fe0
 </TASK>

Crashes (207):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/24 17:27 upstream 38fec10eb60d 875573af .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-snapshot-upstream-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/13 13:50 upstream b7f94fcf5546 44be8b44 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-snapshot-upstream-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/07 07:12 upstream f315296c92fd 831e3629 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-snapshot-upstream-root possible deadlock in ext4_xattr_inode_lookup_create
2024/10/30 14:12 upstream c1e939a21eb1 f3a00767 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in ext4_xattr_inode_lookup_create
2024/09/25 19:15 linux-next 2b7275670032 349a68c4 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/02/14 04:31 upstream ab68d7eb7b1a d9a046cf .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/15 22:03 upstream 546bce579204 d6b2ee52 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/15 21:33 upstream 546bce579204 d6b2ee52 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/15 15:25 upstream 546bce579204 d6b2ee52 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/15 15:01 upstream 546bce579204 d6b2ee52 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/15 13:29 upstream 546bce579204 d6b2ee52 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/10 06:00 upstream 3013c33dcbd9 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/09 23:08 upstream 3013c33dcbd9 bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/09 09:53 upstream 9c69f8884904 bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/09 08:13 upstream 9c69f8884904 bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/08 16:13 upstream d76bb1ebb558 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/08 08:13 upstream d76bb1ebb558 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/08 02:29 upstream d76bb1ebb558 dbf35fa1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/07 20:58 upstream 707df3375124 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/03 22:56 upstream 95d3481af6dc b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/03 16:31 upstream 95d3481af6dc b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/30 08:21 upstream 8bac8898fe39 85a5a23f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/30 05:55 upstream 8bac8898fe39 85a5a23f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/30 05:02 upstream 8bac8898fe39 85a5a23f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/29 02:46 upstream f15d97df5afa c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/29 02:34 upstream f15d97df5afa c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/29 00:47 upstream f15d97df5afa c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/29 00:45 upstream f15d97df5afa c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/28 22:26 upstream f15d97df5afa c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/03 16:59 upstream a2cc6ff5ec8f 996a9618 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/02 06:45 upstream acc4d5ff0b61 c799dfdd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/30 22:55 upstream aa918db707fb d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/30 08:43 upstream 7f2ff7b62617 d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/29 18:41 upstream 7d06015d936c d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/27 16:13 upstream 1e1ba8d23dae 20510e88 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/26 04:19 upstream 2df0c02dab82 89d30d73 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/25 21:33 upstream 2df0c02dab82 89d30d73 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/25 20:14 upstream 2df0c02dab82 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/24 16:55 upstream 38fec10eb60d 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/24 01:08 upstream 586de92313fc 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/23 10:08 upstream 586de92313fc 4e8d3850 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/22 04:34 upstream 88d324e69ea9 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/19 23:56 upstream a7f2e10ecd8f 3b7445cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/17 22:14 upstream 4701f33a1070 ce3352cd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/14 14:06 upstream 695caca9345a e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/12 17:05 upstream 0fed89a961ea ee70e6db .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/03/12 07:34 upstream 0fed89a961ea ee70e6db .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/04/18 17:50 upstream fc96b232f8e7 2a20f901 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-snapshot-upstream-root possible deadlock in ext4_xattr_inode_lookup_create
2024/11/26 07:01 linux-next ed9a4ad6e5bd a84878fc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_xattr_inode_lookup_create
2025/05/07 08:48 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e0f4c8dd9d2d 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_xattr_inode_lookup_create
2025/05/06 12:57 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e0f4c8dd9d2d ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_xattr_inode_lookup_create
2025/05/06 05:32 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e0f4c8dd9d2d ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_xattr_inode_lookup_create
* Struck through repros no longer work on HEAD.