syzbot


possible deadlock in ext4_xattr_inode_iget

Status: upstream: reported C repro on 2023/03/12 00:08
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+008d00e9bf75d9de62c7@syzkaller.appspotmail.com
First crash: 460d, last: 17d
Bug presence (1)
Date Name Commit Repro Result
2023/05/08 upstream (ToT) ba0ad6ed89fd C [report] possible deadlock in ext4_xattr_inode_iget
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in ext4_xattr_inode_iget ext4 C done 351 358d 515d 22/27 fixed on 2023/07/01 16:05
upstream possible deadlock in ext4_xattr_inode_iget (2) ext4 C done done 22 150d 343d 26/27 fixed on 2024/03/20 11:33
linux-6.1 possible deadlock in ext4_xattr_inode_iget origin:upstream C error 40 48d 459d 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 49d 72d 0/27 upstream: reported C repro on 2024/04/03 07:45
Fix bisection attempts (7)
Created Duration User Patch Repo Result
2024/04/30 22:23 1h21m bisect fix linux-5.15.y job log (0) log
2024/03/31 05:40 1h20m bisect fix linux-5.15.y job log (0) log
2024/02/29 21:02 55m bisect fix linux-5.15.y job log (0) log
2024/01/20 14:07 42m bisect fix linux-5.15.y job log (0) log
2023/12/20 22:43 1h15m bisect fix linux-5.15.y job log (0) log
2023/11/20 19:28 1h10m bisect fix linux-5.15.y job log (0) log
2023/10/19 17:15 50m bisect fix linux-5.15.y job log (0) log

Sample crash report:
loop0: detected capacity change from 0 to 512
EXT4-fs (loop0): Warning: mounting with an experimental mount option 'dioread_nolock' for blocksize < PAGE_SIZE
EXT4-fs (loop0): 1 truncate cleaned up
EXT4-fs (loop0): mounted filesystem without journal. Opts: inode_readahead_blks=0x0000000000000000,nogrpid,debug_want_extra_isize=0x0000000000000066,dioread_nolock,max_batch_time=0x0000000000000008,resgid=0x0000000000000000,,errors=continue. Quota mode: writeback.
======================================================
WARNING: possible circular locking dependency detected
5.15.110-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor307/3497 is trying to acquire lock:
ffff888074d45da8 (&ea_inode->i_rwsem#9/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
ffff888074d45da8 (&ea_inode->i_rwsem#9/1){+.+.}-{3:3}, at: ext4_xattr_inode_iget+0x4a3/0x5e0 fs/ext4/xattr.c:438

but task is already holding lock:
ffff888074d45238 (&ei->i_data_sem){++++}-{3:3}, at: ext4_setattr+0x1322/0x1990 fs/ext4/inode.c:5486

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ei->i_data_sem){++++}-{3:3}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
       down_write+0x97/0x170 kernel/locking/rwsem.c:1541
       ext4_update_i_disksize fs/ext4/ext4.h:3407 [inline]
       ext4_xattr_inode_write fs/ext4/xattr.c:1413 [inline]
       ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1562 [inline]
       ext4_xattr_set_entry+0x3187/0x3c00 fs/ext4/xattr.c:1686
       ext4_xattr_ibody_set+0x11d/0x330 fs/ext4/xattr.c:2238
       ext4_xattr_set_handle+0xc72/0x1560 fs/ext4/xattr.c:2395
       ext4_xattr_set+0x231/0x3d0 fs/ext4/xattr.c:2508
       __vfs_setxattr+0x3e7/0x420 fs/xattr.c:182
       __vfs_setxattr_noperm+0x12a/0x5e0 fs/xattr.c:216
       vfs_setxattr+0x21d/0x420 fs/xattr.c:303
       do_setxattr fs/xattr.c:588 [inline]
       setxattr+0x27e/0x2e0 fs/xattr.c:611
       path_setxattr+0x1bc/0x2a0 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+0x3d/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x61/0xcb

-> #0 (&ea_inode->i_rwsem#9/1){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain+0x1646/0x58b0 kernel/locking/lockdep.c:3787
       __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
       down_write+0x97/0x170 kernel/locking/rwsem.c:1541
       inode_lock include/linux/fs.h:787 [inline]
       ext4_xattr_inode_iget+0x4a3/0x5e0 fs/ext4/xattr.c:438
       ext4_xattr_inode_get+0x17d/0x9a0 fs/ext4/xattr.c:501
       ext4_xattr_move_to_block fs/ext4/xattr.c:2589 [inline]
       ext4_xattr_make_inode_space fs/ext4/xattr.c:2691 [inline]
       ext4_expand_extra_isize_ea+0xe77/0x1bc0 fs/ext4/xattr.c:2783
       __ext4_expand_extra_isize+0x2f7/0x3d0 fs/ext4/inode.c:5828
       ext4_try_to_expand_extra_isize fs/ext4/inode.c:5871 [inline]
       __ext4_mark_inode_dirty+0x539/0x860 fs/ext4/inode.c:5949
       ext4_setattr+0x13b0/0x1990 fs/ext4/inode.c:5489
       notify_change+0xd4d/0x1000 fs/attr.c:488
       do_truncate+0x21c/0x300 fs/open.c:65
       handle_truncate fs/namei.c:3195 [inline]
       do_open fs/namei.c:3542 [inline]
       path_openat+0x28a0/0x2f20 fs/namei.c:3672
       do_filp_open+0x21c/0x460 fs/namei.c:3699
       do_sys_openat2+0x13b/0x500 fs/open.c:1211
       do_sys_open fs/open.c:1227 [inline]
       __do_sys_creat fs/open.c:1301 [inline]
       __se_sys_creat fs/open.c:1295 [inline]
       __x64_sys_creat+0x11f/0x160 fs/open.c:1295
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x61/0xcb

other info that might help us debug this:

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

5 locks held by syz-executor307/3497:
 #0: ffff888015da6460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
 #1: ffff888074d453b0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff888074d453b0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: do_truncate+0x208/0x300 fs/open.c:63
 #2: ffff888074d45550 (mapping.invalidate_lock){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:832 [inline]
 #2: ffff888074d45550 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_setattr+0xdaa/0x1990 fs/ext4/inode.c:5446
 #3: ffff888074d45238 (&ei->i_data_sem){++++}-{3:3}, at: ext4_setattr+0x1322/0x1990 fs/ext4/inode.c:5486
 #4: ffff888074d45088 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:162 [inline]
 #4: ffff888074d45088 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:5868 [inline]
 #4: ffff888074d45088 (&ei->xattr_sem){++++}-{3:3}, at: __ext4_mark_inode_dirty+0x4a0/0x860 fs/ext4/inode.c:5949

stack backtrace:
CPU: 1 PID: 3497 Comm: syz-executor307 Not tainted 5.15.110-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 check_noncircular+0x2f8/0x3b0 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+0x1646/0x58b0 kernel/locking/lockdep.c:3787
 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5622
 down_write+0x97/0x170 kernel/locking/rwsem.c:1541
 inode_lock include/linux/fs.h:787 [inline]
 ext4_xattr_inode_iget+0x4a3/0x5e0 fs/ext4/xattr.c:438
 ext4_xattr_inode_get+0x17d/0x9a0 fs/ext4/xattr.c:501
 ext4_xattr_move_to_block fs/ext4/xattr.c:2589 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2691 [inline]
 ext4_expand_extra_isize_ea+0xe77/0x1bc0 fs/ext4/xattr.c:2783
 __ext4_expand_extra_isize+0x2f7/0x3d0 fs/ext4/inode.c:5828
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5871 [inline]
 __ext4_mark_inode_dirty+0x539/0x860 fs/ext4/inode.c:5949
 ext4_setattr+0x13b0/0x1990 fs/ext4/inode.c:5489
 notify_change+0xd4d/0x1000 fs/attr.c:488
 do_truncate+0x21c/0x300 fs/open.c:65
 handle_truncate fs/namei.c:3195 [inline]
 do_open fs/namei.c:3542 [inline]
 path_openat+0x28a0/0x2f20 fs/namei.c:3672
 do_filp_open+0x21c/0x460 fs/namei.c:3699
 do_sys_openat2+0x13b/0x500 fs/open.c:1211
 do_sys_open fs/open.c:1227 [inline]
 __do_sys_creat fs/open.c:1301 [inline]
 __se_sys_creat fs/open.c:1295 [inline]
 __x64_sys_creat+0x11f/0x160 fs/open.c:1295
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fb3256a0c29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 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:00007ffc984d49d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda

Crashes (68):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/05/08 03:28 linux-5.15.y 8a7f2a5c5aa1 90c93c40 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2024/05/27 22:09 linux-5.15.y c61bd26ae81a 761766e6 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in ext4_xattr_inode_iget
2024/05/27 05:27 linux-5.15.y c61bd26ae81a a10a183e .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in ext4_xattr_inode_iget
2023/06/25 00:15 linux-5.15.y f67653019430 79782afc .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/06/09 02:41 linux-5.15.y d7af3e5ba454 058b3a5a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/06/03 20:31 linux-5.15.y 0ab06468cbd1 a4ae4f42 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/06/03 20:10 linux-5.15.y 0ab06468cbd1 a4ae4f42 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/06/03 19:49 linux-5.15.y 0ab06468cbd1 a4ae4f42 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/06/03 19:28 linux-5.15.y 0ab06468cbd1 a4ae4f42 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/09/19 04:51 linux-5.15.y aff03380bda4 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ext4_xattr_inode_iget
2023/08/23 05:47 linux-5.15.y f6f7927ac664 b81ca3f6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/08/16 23:19 linux-5.15.y f6f7927ac664 74b106b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/29 02:48 linux-5.15.y 1fe619a7d252 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/18 04:41 linux-5.15.y 9d6bde853685 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/17 15:19 linux-5.15.y 9d6bde853685 eaac4681 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/16 23:22 linux-5.15.y b0ece631f84a 11c89444 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/16 18:23 linux-5.15.y b0ece631f84a 11c89444 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/16 03:04 linux-5.15.y b0ece631f84a 71b00cfb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/15 20:50 linux-5.15.y b0ece631f84a c4d362e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/15 15:07 linux-5.15.y b0ece631f84a c4d362e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/15 10:57 linux-5.15.y b0ece631f84a c4d362e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/13 20:32 linux-5.15.y b0ece631f84a 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/13 15:46 linux-5.15.y b0ece631f84a 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/13 13:38 linux-5.15.y b0ece631f84a 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/13 11:58 linux-5.15.y b0ece631f84a 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/13 05:13 linux-5.15.y b0ece631f84a ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/13 01:27 linux-5.15.y b0ece631f84a ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/13 01:26 linux-5.15.y b0ece631f84a ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/13 01:26 linux-5.15.y b0ece631f84a ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/12 21:33 linux-5.15.y b0ece631f84a ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/12 14:44 linux-5.15.y b0ece631f84a ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/12 07:32 linux-5.15.y b0ece631f84a adb9a3cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/12 06:39 linux-5.15.y b0ece631f84a adb9a3cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/11 18:03 linux-5.15.y b0ece631f84a 0fbd49f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/11 11:56 linux-5.15.y 8a7f2a5c5aa1 0fbd49f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/11 10:11 linux-5.15.y 8a7f2a5c5aa1 0fbd49f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/11 07:26 linux-5.15.y 8a7f2a5c5aa1 0fbd49f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/10 23:08 linux-5.15.y 8a7f2a5c5aa1 14b12a99 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/10 23:08 linux-5.15.y 8a7f2a5c5aa1 14b12a99 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/10 19:44 linux-5.15.y 8a7f2a5c5aa1 14b12a99 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/10 19:30 linux-5.15.y 8a7f2a5c5aa1 14b12a99 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/10 10:59 linux-5.15.y 8a7f2a5c5aa1 14b12a99 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/10 06:41 linux-5.15.y 8a7f2a5c5aa1 1964022b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 22:48 linux-5.15.y 8a7f2a5c5aa1 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 21:28 linux-5.15.y 8a7f2a5c5aa1 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 19:35 linux-5.15.y 8a7f2a5c5aa1 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 17:47 linux-5.15.y 8a7f2a5c5aa1 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 17:01 linux-5.15.y 8a7f2a5c5aa1 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 13:40 linux-5.15.y 8a7f2a5c5aa1 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 09:33 linux-5.15.y 8a7f2a5c5aa1 c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 09:30 linux-5.15.y 8a7f2a5c5aa1 c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 09:21 linux-5.15.y 8a7f2a5c5aa1 c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 08:01 linux-5.15.y 8a7f2a5c5aa1 c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 05:35 linux-5.15.y 8a7f2a5c5aa1 c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 04:17 linux-5.15.y 8a7f2a5c5aa1 c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/09 01:03 linux-5.15.y 8a7f2a5c5aa1 c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/08 22:13 linux-5.15.y 8a7f2a5c5aa1 c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/08 20:18 linux-5.15.y 8a7f2a5c5aa1 c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/08 03:46 linux-5.15.y 8a7f2a5c5aa1 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/08 03:37 linux-5.15.y 8a7f2a5c5aa1 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/08 03:36 linux-5.15.y 8a7f2a5c5aa1 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/08 03:34 linux-5.15.y 8a7f2a5c5aa1 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/08 03:26 linux-5.15.y 8a7f2a5c5aa1 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/08 03:16 linux-5.15.y 8a7f2a5c5aa1 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/05/08 03:11 linux-5.15.y 8a7f2a5c5aa1 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
2023/03/12 00:08 linux-5.15.y d214f240b0f6 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ext4_xattr_inode_iget
* Struck through repros no longer work on HEAD.