syzbot


possible deadlock in ext4_xattr_inode_iget

Status: fixed on 2023/07/01 16:05
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+298c5d8fb4a128bc27b0@syzkaller.appspotmail.com
Fix commit: aff3bea95388 ext4: add lockdep annotations for i_data_sem for ea_inode's
First crash: 494d, last: 333d
Cause bisection: introduced by (bisect log) :
commit a3c06ae158dd6fa8336157c31d9234689d068d02
Author: Parav Pandit <parav@nvidia.com>
Date: Tue Jan 5 10:32:03 2021 +0000

  vdpa_sim_net: Add support for user supported devices

Crash: possible deadlock in ext4_xattr_inode_iget (log)
Repro: C syz .config
  
Discussions (2)
Title Replies (including bot) Last reply
[PATCH 0/4] ext4: clean up ea_inode handling 5 (5) 2023/05/24 03:49
[syzbot] [ext4?] possible deadlock in ext4_xattr_inode_iget 0 (3) 2023/05/08 10:39
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in ext4_xattr_inode_iget (2) ext4 C done done 22 125d 318d 26/26 fixed on 2024/03/20 11:33
linux-5.15 possible deadlock in ext4_xattr_inode_iget origin:upstream C 66 19d 435d 0/3 upstream: reported C repro on 2023/03/12 00:08
linux-6.1 possible deadlock in ext4_xattr_inode_iget origin:upstream C 40 23d 435d 0/3 upstream: reported C repro on 2023/03/12 10:40
upstream possible deadlock in ext4_xattr_inode_iget (3) ext4 C error 2 24d 47d 0/26 upstream: reported C repro on 2024/04/03 07:45
Last patch testing requests (2)
Created Duration User Patch Repo Result
2023/05/23 16:23 13m tytso@mit.edu git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git test report log
2023/05/22 19:16 13m tytso@mit.edu git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git test report log

Sample crash report:
loop0: detected capacity change from 0 to 512
EXT4-fs: Warning: mounting with an experimental mount option 'dioread_nolock' for blocksize < PAGE_SIZE
EXT4-fs (loop0): 1 truncate cleaned up
======================================================
WARNING: possible circular locking dependency detected
6.4.0-rc7-syzkaller-00072-gdad9774deaf1 #0 Not tainted
------------------------------------------------------
syz-executor162/5119 is trying to acquire lock:
ffff888073d04000 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
ffff888073d04000 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: ext4_xattr_inode_iget+0x173/0x400 fs/ext4/xattr.c:461

but task is already holding lock:
ffff888073d04888 (&ei->i_data_sem/3){++++}-{3:3}, at: ext4_setattr+0x1988/0x2880 fs/ext4/inode.c:5423

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+0x92/0x200 kernel/locking/rwsem.c:1573
       ext4_update_i_disksize fs/ext4/ext4.h:3309 [inline]
       ext4_xattr_inode_write fs/ext4/xattr.c:1446 [inline]
       ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1594 [inline]
       ext4_xattr_set_entry+0x3046/0x3810 fs/ext4/xattr.c:1719
       ext4_xattr_ibody_set+0x131/0x3a0 fs/ext4/xattr.c:2273
       ext4_xattr_set_handle+0x968/0x1510 fs/ext4/xattr.c:2430
       ext4_xattr_set+0x144/0x360 fs/ext4/xattr.c:2544
       __vfs_setxattr+0x173/0x1e0 fs/xattr.c:201
       __vfs_setxattr_noperm+0x129/0x5f0 fs/xattr.c:235
       __vfs_setxattr_locked+0x1d3/0x260 fs/xattr.c:296
       vfs_setxattr+0x143/0x340 fs/xattr.c:322
       do_setxattr+0x147/0x190 fs/xattr.c:630
       setxattr+0x146/0x160 fs/xattr.c:653
       path_setxattr+0x197/0x1c0 fs/xattr.c:672
       __do_sys_setxattr fs/xattr.c:688 [inline]
       __se_sys_setxattr fs/xattr.c:684 [inline]
       __x64_sys_setxattr+0xc4/0x160 fs/xattr.c:684
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3113 [inline]
       check_prevs_add kernel/locking/lockdep.c:3232 [inline]
       validate_chain kernel/locking/lockdep.c:3847 [inline]
       __lock_acquire+0x2fcd/0x5f30 kernel/locking/lockdep.c:5088
       lock_acquire kernel/locking/lockdep.c:5705 [inline]
       lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5670
       down_write+0x92/0x200 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:775 [inline]
       ext4_xattr_inode_iget+0x173/0x400 fs/ext4/xattr.c:461
       ext4_xattr_inode_get+0x162/0x830 fs/ext4/xattr.c:535
       ext4_xattr_move_to_block fs/ext4/xattr.c:2626 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2728 [inline]
       ext4_expand_extra_isize_ea+0xf51/0x1810 fs/ext4/xattr.c:2820
       __ext4_expand_extra_isize+0x33e/0x470 fs/ext4/inode.c:5795
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:5838 [inline]
       __ext4_mark_inode_dirty+0x51b/0x800 fs/ext4/inode.c:5916
       ext4_setattr+0x1a02/0x2880 fs/ext4/inode.c:5426
       notify_change+0xb2c/0x1180 fs/attr.c:483
       do_truncate+0x143/0x200 fs/open.c:66
       handle_truncate fs/namei.c:3295 [inline]
       do_open fs/namei.c:3640 [inline]
       path_openat+0x2083/0x2750 fs/namei.c:3791
       do_filp_open+0x1ba/0x410 fs/namei.c:3818
       do_sys_openat2+0x16d/0x4c0 fs/open.c:1356
       do_sys_open fs/open.c:1372 [inline]
       __do_sys_creat fs/open.c:1448 [inline]
       __se_sys_creat fs/open.c:1442 [inline]
       __x64_sys_creat+0xcd/0x120 fs/open.c:1442
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ei->i_data_sem/3);
                               lock(&ea_inode->i_rwsem#8/1);
                               lock(&ei->i_data_sem/3);
  lock(&ea_inode->i_rwsem#8/1);

 *** DEADLOCK ***

5 locks held by syz-executor162/5119:
 #0: ffff88807c0f4460 (sb_writers#4){.+.+}-{0:0}, at: do_open fs/namei.c:3629 [inline]
 #0: ffff88807c0f4460 (sb_writers#4){.+.+}-{0:0}, at: path_openat+0x19a4/0x2750 fs/namei.c:3791
 #1: ffff888073d04a00 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
 #1: ffff888073d04a00 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: do_truncate+0x131/0x200 fs/open.c:64
 #2: ffff888073d04ba0 (mapping.invalidate_lock){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:820 [inline]
 #2: ffff888073d04ba0 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_setattr+0x6f2/0x2880 fs/ext4/inode.c:5383
 #3: ffff888073d04888 (&ei->i_data_sem/3){++++}-{3:3}, at: ext4_setattr+0x1988/0x2880 fs/ext4/inode.c:5423
 #4: ffff888073d046c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:162 [inline]
 #4: ffff888073d046c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:5835 [inline]
 #4: ffff888073d046c8 (&ei->xattr_sem){++++}-{3:3}, at: __ext4_mark_inode_dirty+0x48f/0x800 fs/ext4/inode.c:5916

stack backtrace:
CPU: 1 PID: 5119 Comm: syz-executor162 Not tainted 6.4.0-rc7-syzkaller-00072-gdad9774deaf1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2188
 check_prev_add kernel/locking/lockdep.c:3113 [inline]
 check_prevs_add kernel/locking/lockdep.c:3232 [inline]
 validate_chain kernel/locking/lockdep.c:3847 [inline]
 __lock_acquire+0x2fcd/0x5f30 kernel/locking/lockdep.c:5088
 lock_acquire kernel/locking/lockdep.c:5705 [inline]
 lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5670
 down_write+0x92/0x200 kernel/locking/rwsem.c:1573
 inode_lock include/linux/fs.h:775 [inline]
 ext4_xattr_inode_iget+0x173/0x400 fs/ext4/xattr.c:461
 ext4_xattr_inode_get+0x162/0x830 fs/ext4/xattr.c:535
 ext4_xattr_move_to_block fs/ext4/xattr.c:2626 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2728 [inline]
 ext4_expand_extra_isize_ea+0xf51/0x1810 fs/ext4/xattr.c:2820
 __ext4_expand_extra_isize+0x33e/0x470 fs/ext4/inode.c:5795
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5838 [inline]
 __ext4_mark_inode_dirty+0x51b/0x800 fs/ext4/inode.c:5916
 ext4_setattr+0x1a02/0x2880 fs/ext4/inode.c:5426
 notify_change+0xb2c/0x1180 fs/attr.c:483
 do_truncate+0x143/0x200 fs/open.c:66
 handle_truncate fs/namei.c:3295 [inline]
 do_open fs/namei.c:3640 [inline]
 path_openat+0x2083/0x2750 fs/namei.c:3791
 do_filp_open+0x1ba/0x410 fs/namei.c:3818
 do_sys_openat2+0x16d/0x4c0 fs/open.c:1356
 do_sys_open fs/open.c:1372 [inline]
 __do_sys_creat fs/open.c:1448 [inline]
 __se_sys_creat fs/open.c:1442 [inline]
 __x64_sys_creat+0xcd/0x120 fs/open.c:1442
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f3f30ddca39
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 15 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe3ca2c098 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007f3f30ddca39
RDX: 00007f3f30ddca39 RSI: 0000000000000000 RDI: 0000000020000040
RBP: 0000000000000000 R08: 00007ffe3ca2c0c0 R09: 00007ffe3ca2c0c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe3ca2c0bc
R13: 00007ffe3ca2c0f0 R14: 00007ffe3ca2c0d0 R15: 000000000000003a
 </TASK>

Crashes (351):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/06/22 07:10 upstream dad9774deaf1 09ffe269 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/06/19 20:24 upstream 45a3e24f65e9 d521bc56 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/06/19 20:01 upstream 45a3e24f65e9 d521bc56 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/06/19 19:36 upstream 45a3e24f65e9 d521bc56 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/06/19 19:09 upstream 45a3e24f65e9 d521bc56 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/08 04:16 upstream 17784de648be 90c93c40 .config strace log report syz C [mounted in repro] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/08 03:21 linux-next 83e5775d7afd 90c93c40 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/24 07:37 upstream 27e462c8fad4 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/23 01:59 upstream 421ca22e3138 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/22 14:13 upstream 44c026a73be8 4bce1a3e .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/21 21:08 upstream e2065b8c1b01 4bce1a3e .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/20 11:32 upstream d635f6cc934b 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/19 23:58 upstream cbd6ac3837cd 96689200 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/19 13:31 upstream 2d1bcbc6cd70 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/19 08:04 upstream 2d1bcbc6cd70 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/19 04:13 upstream 2d1bcbc6cd70 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/18 18:01 upstream 4d6d4c7f541d 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/17 14:29 upstream f1fcbaa18b28 eaac4681 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/17 12:22 upstream f1fcbaa18b28 eaac4681 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/17 10:10 upstream f1fcbaa18b28 eaac4681 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/17 08:36 upstream f1fcbaa18b28 eaac4681 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/16 21:54 upstream f1fcbaa18b28 11c89444 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/16 19:30 upstream f1fcbaa18b28 11c89444 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in ext4_xattr_inode_iget
2023/05/16 17:00 upstream f1fcbaa18b28 11c89444 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/16 16:28 upstream f1fcbaa18b28 11c89444 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/16 13:24 upstream f1fcbaa18b28 11c89444 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/16 10:15 upstream f1fcbaa18b28 71b00cfb .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/16 02:05 upstream f1fcbaa18b28 71b00cfb .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/16 00:43 upstream f1fcbaa18b28 71b00cfb .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/15 23:10 upstream f1fcbaa18b28 71b00cfb .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/15 16:02 upstream f1fcbaa18b28 b8bae4ab .config console log report info ci-qemu-upstream possible deadlock in ext4_xattr_inode_iget
2023/05/15 13:46 upstream f1fcbaa18b28 b8bae4ab .config console log report info ci-qemu-upstream possible deadlock in ext4_xattr_inode_iget
2023/05/15 03:14 upstream f1fcbaa18b28 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/14 23:02 upstream 838a854820ee 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/14 21:35 upstream 31f4104e392a 2b9ba477 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in ext4_xattr_inode_iget
2023/05/14 12:39 upstream bb7c241fae62 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in ext4_xattr_inode_iget
2023/05/14 12:16 upstream bb7c241fae62 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/14 11:01 upstream bb7c241fae62 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/14 09:38 upstream bb7c241fae62 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/14 06:01 upstream bb7c241fae62 2b9ba477 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in ext4_xattr_inode_iget
2023/05/14 04:04 upstream d4d58949a6ea 2b9ba477 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/13 23:34 upstream d4d58949a6ea 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/13 20:52 upstream d4d58949a6ea 2b9ba477 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/13 19:41 upstream d4d58949a6ea 2b9ba477 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/13 18:27 upstream d4d58949a6ea 2b9ba477 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/05/13 17:09 upstream d4d58949a6ea 2b9ba477 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_xattr_inode_iget
2023/01/11 12:21 upstream 7dd4b804e080 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/13 05:01 upstream 76c7f8873a76 2b9ba477 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in ext4_xattr_inode_iget
2023/05/18 06:44 linux-next 715abedee4cd 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/18 03:26 linux-next 715abedee4cd 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/16 23:53 linux-next 715abedee4cd 11c89444 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/16 04:19 linux-next 715abedee4cd 71b00cfb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/15 21:16 linux-next 715abedee4cd 71b00cfb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_xattr_inode_iget
2023/05/29 08:13 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci eb0f1697d729 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_xattr_inode_iget
* Struck through repros no longer work on HEAD.