syzbot


possible deadlock in ocfs2_xattr_set

Status: upstream: reported on 2024/09/10 05:07
Subsystems: ocfs2
[Documentation on labels]
Reported-by: syzbot+ba9a789bd1f4d21fcefe@syzkaller.appspotmail.com
First crash: 602d, last: 12h23m
✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision Error
5dfa1376-cebf-413a-8114-e44dd8827d7c repro possible deadlock in ocfs2_xattr_set 2026/03/10 13:47 2026/03/11 10:39 2026/03/11 11:03 86914af9098a80da53c3c5d46be980c572ee29f8
Discussions (18)
Title Replies (including bot) Last reply
[syzbot] Monthly ocfs2 report (Mar 2026) 0 (1) 2026/03/09 12:29
[syzbot] Monthly ocfs2 report (Feb 2026) 0 (1) 2026/02/05 12:34
[syzbot] Monthly ocfs2 report (Jan 2026) 0 (1) 2026/01/05 08:20
[syzbot] Monthly ocfs2 report (Dec 2025) 0 (1) 2025/12/04 23:06
[syzbot] Monthly ocfs2 report (Nov 2025) 0 (1) 2025/11/03 13:10
[syzbot] Monthly ocfs2 report (Oct 2025) 0 (1) 2025/10/03 06:37
[syzbot] Monthly ocfs2 report (Sep 2025) 0 (1) 2025/09/02 09:20
[syzbot] Monthly ocfs2 report (Aug 2025) 0 (1) 2025/08/01 13:49
[syzbot] Monthly ocfs2 report (Jul 2025) 0 (1) 2025/07/01 10:01
[syzbot] Monthly ocfs2 report (May 2025) 0 (1) 2025/06/03 11:11
[syzbot] Monthly ocfs2 report (Apr 2025) 0 (1) 2025/04/29 12:47
[syzbot] Monthly ocfs2 report (Mar 2025) 0 (1) 2025/03/31 13:08
[syzbot] Monthly ocfs2 report (Feb 2025) 0 (1) 2025/02/26 12:08
[syzbot] Monthly ocfs2 report (Dec 2024) 0 (1) 2024/12/26 08:58
[syzbot] Monthly ocfs2 report (Nov 2024) 0 (1) 2024/11/25 10:35
[syzbot] Monthly ocfs2 report (Oct 2024) 0 (1) 2024/10/24 08:02
[syzbot] Monthly ocfs2 report (Sep 2024) 0 (1) 2024/09/23 09:03
[syzbot] [ocfs2?] possible deadlock in ocfs2_xattr_set 0 (1) 2024/09/10 05:07
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in ocfs2_xattr_set 4 464 1d16h 594d 0/3 upstream: reported on 2024/09/14 01:11
linux-6.6 possible deadlock in ocfs2_xattr_set 4 410 1d13h 315d 0/2 upstream: reported on 2025/06/19 18:15
linux-6.1 possible deadlock in ocfs2_xattr_set 4 826 16h26m 582d 0/3 upstream: reported on 2024/09/25 09:02

Sample crash report:
loop0: detected capacity change from 0 to 32768
JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.0.7364/29506 is trying to acquire lock:
ffff88806a9deba0 (&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1029 [inline]
ffff88806a9deba0 (&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_xattr_set+0xba7/0x13e0 fs/ocfs2/xattr.c:3653

but task is already holding lock:
ffff88806a9df6e8 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_xattr_set+0x475/0x13e0 fs/ocfs2/xattr.c:3614

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&oi->ip_xattr_sem){++++}-{4:4}:
       down_read+0x47/0x2e0 kernel/locking/rwsem.c:1568
       ocfs2_init_acl+0x2fd/0x7e0 fs/ocfs2/acl.c:367
       ocfs2_mknod+0x1679/0x2260 fs/ocfs2/namei.c:414
       ocfs2_mkdir+0x181/0x460 fs/ocfs2/namei.c:660
       vfs_mkdir+0x413/0x630 fs/namei.c:5261
       filename_mkdirat+0x285/0x510 fs/namei.c:5294
       __do_sys_mkdirat fs/namei.c:5315 [inline]
       __se_sys_mkdirat+0x35/0x150 fs/namei.c:5312
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&journal->j_trans_barrier){.+.+}-{4:4}:
       down_read+0x47/0x2e0 kernel/locking/rwsem.c:1568
       ocfs2_start_trans+0x3ab/0x700 fs/ocfs2/journal.c:369
       ocfs2_mknod+0x1181/0x2260 fs/ocfs2/namei.c:365
       ocfs2_create+0x195/0x460 fs/ocfs2/namei.c:677
       lookup_open fs/namei.c:4511 [inline]
       open_last_lookups fs/namei.c:4611 [inline]
       path_openat+0x1395/0x3860 fs/namei.c:4855
       do_file_open+0x23e/0x4a0 fs/namei.c:4887
       do_sys_openat2+0x113/0x200 fs/open.c:1364
       do_sys_open fs/open.c:1370 [inline]
       __do_sys_openat fs/open.c:1386 [inline]
       __se_sys_openat fs/open.c:1381 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1381
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (sb_internal#3){.+.+}-{0:0}:
       percpu_down_read_internal include/linux/percpu-rwsem.h:53 [inline]
       percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline]
       __sb_start_write include/linux/fs/super.h:19 [inline]
       sb_start_intwrite include/linux/fs/super.h:177 [inline]
       ocfs2_start_trans+0x2ac/0x700 fs/ocfs2/journal.c:367
       ocfs2_remove_btree_range+0x84c/0x1610 fs/ocfs2/alloc.c:5769
       ocfs2_commit_truncate+0xbb8/0x2310 fs/ocfs2/alloc.c:7383
       ocfs2_truncate_for_delete fs/ocfs2/inode.c:701 [inline]
       ocfs2_wipe_inode fs/ocfs2/inode.c:868 [inline]
       ocfs2_delete_inode fs/ocfs2/inode.c:1157 [inline]
       ocfs2_evict_inode+0x1023/0x43b0 fs/ocfs2/inode.c:1299
       evict+0x61e/0xb10 fs/inode.c:841
       ocfs2_dentry_iput+0x24d/0x390 fs/ocfs2/dcache.c:407
       __dentry_kill+0x1a2/0x690 fs/dcache.c:718
       finish_dput+0xc9/0x480 fs/dcache.c:927
       end_renaming fs/namei.c:4124 [inline]
       filename_renameat2+0x61e/0x9c0 fs/namei.c:6174
       __do_sys_rename fs/namei.c:6216 [inline]
       __se_sys_rename+0x55/0x2c0 fs/namei.c:6212
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]){+.+.}-{4:4}:
       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+0x106/0x350 kernel/locking/lockdep.c:5868
       down_write+0x96/0x200 kernel/locking/rwsem.c:1625
       inode_lock include/linux/fs.h:1029 [inline]
       ocfs2_xattr_set+0xba7/0x13e0 fs/ocfs2/xattr.c:3653
       __vfs_setxattr+0x43c/0x480 fs/xattr.c:218
       __vfs_setxattr_noperm+0x12d/0x660 fs/xattr.c:252
       vfs_setxattr+0x163/0x360 fs/xattr.c:339
       do_setxattr fs/xattr.c:654 [inline]
       filename_setxattr+0x296/0x630 fs/xattr.c:682
       path_setxattrat+0x3eb/0x440 fs/xattr.c:726
       __do_sys_setxattr fs/xattr.c:760 [inline]
       __se_sys_setxattr fs/xattr.c:756 [inline]
       __x64_sys_setxattr+0xbc/0xe0 fs/xattr.c:756
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x15f/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:
  &ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE] --> &journal->j_trans_barrier --> &oi->ip_xattr_sem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&oi->ip_xattr_sem);
                               lock(&journal->j_trans_barrier);
                               lock(&oi->ip_xattr_sem);
  lock(&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]);

 *** DEADLOCK ***

3 locks held by syz.0.7364/29506:
 #0: ffff888042f00410 (sb_writers#17){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff88806a9df9a0 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1029 [inline]
 #1: ffff88806a9df9a0 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}, at: vfs_setxattr+0x13e/0x360 fs/xattr.c:338
 #2: ffff88806a9df6e8 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_xattr_set+0x475/0x13e0 fs/ocfs2/xattr.c:3614

stack backtrace:
CPU: 0 UID: 0 PID: 29506 Comm: syz.0.7364 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/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+0x106/0x350 kernel/locking/lockdep.c:5868
 down_write+0x96/0x200 kernel/locking/rwsem.c:1625
 inode_lock include/linux/fs.h:1029 [inline]
 ocfs2_xattr_set+0xba7/0x13e0 fs/ocfs2/xattr.c:3653
 __vfs_setxattr+0x43c/0x480 fs/xattr.c:218
 __vfs_setxattr_noperm+0x12d/0x660 fs/xattr.c:252
 vfs_setxattr+0x163/0x360 fs/xattr.c:339
 do_setxattr fs/xattr.c:654 [inline]
 filename_setxattr+0x296/0x630 fs/xattr.c:682
 path_setxattrat+0x3eb/0x440 fs/xattr.c:726
 __do_sys_setxattr fs/xattr.c:760 [inline]
 __se_sys_setxattr fs/xattr.c:756 [inline]
 __x64_sys_setxattr+0xbc/0xe0 fs/xattr.c:756
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f597b59cdd9
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:00007f597c423028 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f597b815fa0 RCX: 00007f597b59cdd9
RDX: 0000000000000000 RSI: 0000200000000080 RDI: 0000200000000040
RBP: 00007f597b632d69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f597b816038 R14: 00007f597b815fa0 R15: 00007ffc45dc4ce8
 </TASK>

Crashes (9084):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/30 20:03 upstream 08d0d3466664 753c55b9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/30 11:33 upstream e75a43c7cec4 005438fc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/28 03:34 upstream 3b3bea6d4b9c ce741359 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/27 19:58 upstream 254f49634ee1 0f700595 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/27 15:40 upstream 254f49634ee1 0f700595 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/26 02:35 upstream 897d54018cc9 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ocfs2_xattr_set
2026/04/21 17:15 upstream b4e07588e743 0b6ab7ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/20 21:46 upstream a5d1079c28a5 e65da4ee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/19 22:58 upstream faeab166167f 303e2802 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/19 21:40 upstream faeab166167f 303e2802 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/19 14:15 upstream faeab166167f 303e2802 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ocfs2_xattr_set
2026/04/15 16:12 upstream 1f5ffc672165 c441f497 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/14 21:17 upstream d60bc1401583 362d1323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/14 17:51 upstream d60bc1401583 362d1323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/14 15:26 upstream d60bc1401583 362d1323 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/14 08:14 upstream 26ff969926a0 1a086e7c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/14 02:28 upstream 26ff969926a0 1a086e7c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/14 00:54 upstream 26ff969926a0 1a086e7c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/13 20:34 upstream 26ff969926a0 9530ccf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/13 19:26 upstream 26ff969926a0 9530ccf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/13 15:16 upstream 028ef9c96e96 9530ccf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/13 13:55 upstream 028ef9c96e96 9530ccf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/13 12:25 upstream 028ef9c96e96 9530ccf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/13 08:23 upstream 028ef9c96e96 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/13 05:33 upstream 028ef9c96e96 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/13 02:00 upstream 028ef9c96e96 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/12 21:00 upstream f5459048c38a 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/12 14:16 upstream f5459048c38a 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/12 12:57 upstream f5459048c38a 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/12 09:45 upstream e753c16cb3dd 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/12 08:04 upstream e753c16cb3dd 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/12 06:59 upstream e753c16cb3dd 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/12 04:46 upstream e753c16cb3dd 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/12 00:52 upstream e753c16cb3dd 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/11 20:48 upstream e774d5f1bc27 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/11 19:42 upstream e774d5f1bc27 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/11 19:13 upstream e774d5f1bc27 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/11 17:51 upstream e774d5f1bc27 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/11 15:13 upstream e774d5f1bc27 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/11 11:52 upstream e774d5f1bc27 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/11 05:22 upstream 7c6c4ed80b87 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/10 23:54 upstream 7c6c4ed80b87 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/03/10 13:20 upstream 1f318b96cc84 6972f302 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/04/06 05:34 upstream 1791c390149f 4440e7c2 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2024/09/07 01:04 upstream b831f83e40a2 ce70880a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2024/09/06 04:58 upstream ad618736883b 464ac2ed .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2026/04/28 16:58 linux-next 9974969c1403 b4209743 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/27 12:45 linux-next 7080e32d3f09 0f700595 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/22 09:47 linux-next bee6ea30c487 0b6ab7ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/04/13 21:45 linux-next 1c7cc4904160 9530ccf9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/02/09 06:29 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 ocfs2_xattr_set
* Struck through repros no longer work on HEAD.