possible deadlock in ocfs2_xattr_set

Status: upstream: reported on 2024/09/10 05:07
Subsystems: ocfs2
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+ba9a789bd1f4d21fcefe@syzkaller.appspotmail.com
First crash: 703d, last: 7h19m
✨ AI Jobs (3)
ID Workflow Result Correct Bug Created Started Finished Revision
95918036 repro-c Reproduced: ✅
possible deadlock in ocfs2_xattr_set 2026/08/06 14:11 2026/08/06 14:11 2026/08/06 17:45 c38879ea
2cc04dad assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ❌ VMHostTrigger: ❌ possible deadlock in ocfs2_xattr_set 2026/05/21 14:12 2026/05/21 14:12 2026/05/21 14:44 d5742584
5dfa1376 repro possible deadlock in ocfs2_xattr_set 2026/03/10 13:47 2026/03/11 10:39 2026/03/11 11:03 86914af9
Discussions (21)
Title Replies (including bot) Last reply
[syzbot] Monthly ocfs2 report (Jul 2026) 0 (1) 2026/07/11 12:32
[syzbot] Monthly ocfs2 report (Jun 2026) 0 (1) 2026/06/10 04:32
[syzbot] Monthly ocfs2 report (May 2026) 0 (1) 2026/05/10 04:32
[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 485 2d03h 695d 0/3 upstream: reported on 2024/09/14 01:11
linux-6.6 possible deadlock in ocfs2_xattr_set 4 447 4d14h 416d 0/2 upstream: reported on 2025/06/19 18:15
linux-6.1 possible deadlock in ocfs2_xattr_set 4 913 4h21m 684d 0/3 upstream: reported on 2024/09/25 09:02
Last patch testing requests (2)
Created Duration User Patch Repo Result
2026/08/07 08:48 21m glider@google.com upstream error
2026/08/06 20:15 22m nogikh@google.com upstream error

Sample crash report:
ocfs2: Mounting device (7,7) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.7.800/10667 is trying to acquire lock:
ffff888054efeba0 (&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
ffff888054efeba0 (&ocfs2_sysfile_lock_key[TRUNCATE_LOG_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_xattr_set+0xbeb/0x13a0 fs/ocfs2/xattr.c:3666

but task is already holding lock:
ffff888054e606e8 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_xattr_set+0x494/0x13a0 fs/ocfs2/xattr.c:3627

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+0x4a/0x330 kernel/locking/rwsem.c:1574
       ocfs2_init_acl+0x2fd/0x7e0 fs/ocfs2/acl.c:367
       ocfs2_mknod+0x166a/0x2240 fs/ocfs2/namei.c:414
       ocfs2_create+0x195/0x460 fs/ocfs2/namei.c:677
       lookup_open fs/namei.c:4508 [inline]
       open_last_lookups fs/namei.c:4608 [inline]
       path_openat+0x133a/0x3830 fs/namei.c:4860
       do_file_open+0x23e/0x4a0 fs/namei.c:4892
       do_sys_openat2+0x115/0x200 fs/open.c:1368
       do_sys_open fs/open.c:1374 [inline]
       __do_sys_openat fs/open.c:1390 [inline]
       __se_sys_openat fs/open.c:1385 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1385
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&journal->j_trans_barrier){.+.+}-{4:4}:
       down_read+0x4a/0x330 kernel/locking/rwsem.c:1574
       ocfs2_start_trans+0x3ab/0x700 fs/ocfs2/journal.c:369
       ocfs2_mknod+0x116a/0x2240 fs/ocfs2/namei.c:365
       ocfs2_create+0x195/0x460 fs/ocfs2/namei.c:677
       lookup_open fs/namei.c:4508 [inline]
       open_last_lookups fs/namei.c:4608 [inline]
       path_openat+0x133a/0x3830 fs/namei.c:4860
       do_file_open+0x23e/0x4a0 fs/namei.c:4892
       do_sys_openat2+0x115/0x200 fs/open.c:1368
       do_sys_open fs/open.c:1374 [inline]
       __do_sys_openat fs/open.c:1390 [inline]
       __se_sys_openat fs/open.c:1385 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1385
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 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+0x819/0x15f0 fs/ocfs2/alloc.c:5769
       ocfs2_remove_inode_range+0xfd8/0x2730 fs/ocfs2/file.c:1919
       __ocfs2_change_file_space+0x838/0xef0 fs/ocfs2/file.c:2040
       ocfs2_fallocate+0x1f5/0x240 fs/ocfs2/file.c:2150
       vfs_fallocate+0x65a/0x7e0 fs/open.c:338
       madvise_remove mm/madvise.c:1038 [inline]
       madvise_vma_behavior+0x2c07/0x4340 mm/madvise.c:1351
       madvise_walk_vmas+0x576/0xb00 mm/madvise.c:1712
       madvise_do_behavior+0x385/0x540 mm/madvise.c:1907
       do_madvise+0x327/0x3a0 mm/madvise.c:2005
       __do_sys_madvise mm/madvise.c:2014 [inline]
       __se_sys_madvise mm/madvise.c:2012 [inline]
       __x64_sys_madvise+0xa6/0xc0 mm/madvise.c:2012
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 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+0x1520/0x2cf0 kernel/locking/lockdep.c:5237
       lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868
       down_write+0x96/0x200 kernel/locking/rwsem.c:1631
       inode_lock include/linux/fs.h:1024 [inline]
       ocfs2_xattr_set+0xbeb/0x13a0 fs/ocfs2/xattr.c:3666
       ocfs2_set_acl+0x6fd/0x7b0 fs/ocfs2/acl.c:255
       ocfs2_iop_set_acl+0x1b1/0x2b0 fs/ocfs2/acl.c:287
       set_posix_acl fs/posix_acl.c:962 [inline]
       vfs_set_acl+0x8a0/0xb50 fs/posix_acl.c:1141
       do_set_acl+0xf5/0x190 fs/posix_acl.c:1286
       do_setxattr fs/xattr.c:659 [inline]
       filename_setxattr+0x305/0x630 fs/xattr.c:690
       path_setxattrat+0x408/0x450 fs/xattr.c:734
       __do_sys_setxattr fs/xattr.c:768 [inline]
       __se_sys_setxattr fs/xattr.c:764 [inline]
       __x64_sys_setxattr+0xbc/0xe0 fs/xattr.c:764
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 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.7.800/10667:
 #0: ffff888044ed8450 (sb_writers#24){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:494
 #1: ffff888054e609a0 (&type->i_mutex_dir_key#13){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
 #1: ffff888054e609a0 (&type->i_mutex_dir_key#13){+.+.}-{4:4}, at: vfs_set_acl+0x368/0xb50 fs/posix_acl.c:1122
 #2: ffff888054e606e8 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_xattr_set+0x494/0x13a0 fs/ocfs2/xattr.c:3627

stack backtrace:
CPU: 0 UID: 0 PID: 10667 Comm: syz.7.800 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/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+0x1520/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868
 down_write+0x96/0x200 kernel/locking/rwsem.c:1631
 inode_lock include/linux/fs.h:1024 [inline]
 ocfs2_xattr_set+0xbeb/0x13a0 fs/ocfs2/xattr.c:3666
 ocfs2_set_acl+0x6fd/0x7b0 fs/ocfs2/acl.c:255
 ocfs2_iop_set_acl+0x1b1/0x2b0 fs/ocfs2/acl.c:287
 set_posix_acl fs/posix_acl.c:962 [inline]
 vfs_set_acl+0x8a0/0xb50 fs/posix_acl.c:1141
 do_set_acl+0xf5/0x190 fs/posix_acl.c:1286
 do_setxattr fs/xattr.c:659 [inline]
 filename_setxattr+0x305/0x630 fs/xattr.c:690
 path_setxattrat+0x408/0x450 fs/xattr.c:734
 __do_sys_setxattr fs/xattr.c:768 [inline]
 __se_sys_setxattr fs/xattr.c:764 [inline]
 __x64_sys_setxattr+0xbc/0xe0 fs/xattr.c:764
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff69959e0d9
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:00007ff69a43f028 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007ff699825fa0 RCX: 00007ff69959e0d9
RDX: 0000200000000100 RSI: 0000200000002a40 RDI: 0000200000002a00
RBP: 00007ff699635024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000024 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff699826038 R14: 00007ff699825fa0 R15: 00007fff5693a928
 </TASK>
OCFS2: ERROR (device loop7): int ocfs2_claim_suballoc_bits(struct ocfs2_alloc_context *, handle_t *, u32, u32, struct ocfs2_suballoc_result *): Chain allocator dinode 71 has 16777215 used bits but only 1024 total
On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted.
OCFS2: File system is now read-only.
(syz.7.800,10667,0):ocfs2_claim_suballoc_bits:2198 ERROR: status = -30
(syz.7.800,10667,1):__ocfs2_claim_clusters:2579 ERROR: status = -30
(syz.7.800,10667,0):__ocfs2_claim_clusters:2587 ERROR: status = -30
(syz.7.800,10667,1):ocfs2_block_group_alloc_contig:553 ERROR: status = -30
(syz.7.800,10667,1):ocfs2_block_group_alloc:827 ERROR: status = -30
(syz.7.800,10667,1):ocfs2_block_group_alloc:880 ERROR: status = -30
(syz.7.800,10667,0):ocfs2_reserve_suballoc_bits:955 ERROR: status = -30
(syz.7.800,10667,0):ocfs2_reserve_suballoc_bits:972 ERROR: status = -30
(syz.7.800,10667,1):ocfs2_reserve_new_metadata_blocks:1112 ERROR: status = -30
(syz.7.800,10667,1):ocfs2_reserve_new_metadata_blocks:1135 ERROR: status = -30
(syz.7.800,10667,1):ocfs2_init_xattr_set_ctxt:3324 ERROR: status = -30
(syz.7.800,10667,1):ocfs2_xattr_set:3681 ERROR: status = -30

Crashes (9331):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/10 04:17 upstream b643e495ae92 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/08/10 00:34 upstream b643e495ae92 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/08/09 21:59 upstream b643e495ae92 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/08/09 20:11 upstream b643e495ae92 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/08/08 05:03 upstream 9a143525f62b e4ef95d6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/08/06 07:27 upstream 0d8395707651 cd5b1963 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ocfs2_xattr_set
2026/08/03 15:22 upstream 075b74841bd0 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ocfs2_xattr_set
2026/08/03 01:06 upstream bd1dde877520 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ocfs2_xattr_set
2026/08/02 23:23 upstream bd1dde877520 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/08/02 14:36 upstream 2d2338c93da7 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/08/02 12:41 upstream 2d2338c93da7 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/08/01 23:00 upstream 2d2338c93da7 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/08/01 19:52 upstream 0131b508c0e2 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/07/31 02:13 upstream 3708dd948844 aaffb173 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/29 03:38 upstream 3b5f4b83c4ab 19622d9d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ocfs2_xattr_set
2026/07/28 11:00 upstream 62cc90241548 45ae1df4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/26 19:23 upstream 3dab139d4795 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/07/26 16:19 upstream 3dab139d4795 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/07/24 22:55 upstream 48a5a7ab8d6a 05b26a28 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/07/23 18:10 upstream 4539944e5151 71a13572 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/23 09:15 upstream 4539944e5151 881ce5c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/21 07:45 upstream b95f03f04d47 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/21 05:28 upstream b95f03f04d47 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/20 17:23 upstream 1590cf032971 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/18 21:08 upstream 1229e2e57a5c 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/18 13:12 upstream 94515f3a7d42 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/17 13:32 upstream fce2dfa773ce 7f27c57a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/17 00:28 upstream 37e2f878a7a6 71b49442 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/16 21:30 upstream 37e2f878a7a6 71b49442 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/16 09:23 upstream 37e2f878a7a6 27a8bd60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/16 01:04 upstream 58717b2a1365 27a8bd60 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/07/15 18:37 upstream 58717b2a1365 a4ed0f4f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/15 14:08 upstream 58717b2a1365 209f0369 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ocfs2_xattr_set
2026/07/15 02:52 upstream 7059bdf4f04a 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ocfs2_xattr_set
2026/07/15 00:06 upstream 3b029c035b34 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/07/14 17:26 upstream 3b029c035b34 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ocfs2_xattr_set
2026/07/14 12:29 upstream 0f26556c5eee 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ocfs2_xattr_set
2026/05/19 16:43 upstream ab5fce87a778 223544dc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root 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/08/08 23:47 upstream a59f57e2aa12 5d63f80b .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2026/08/03 19:05 upstream 075b74841bd0 bdd50915 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2026/08/02 15:55 upstream 2d2338c93da7 e611ffe1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2026/07/29 19:51 upstream fc02acf6ac0c b63596d1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2026/07/28 07:11 upstream 62cc90241548 45ae1df4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2026/07/28 06:52 upstream 62cc90241548 45ae1df4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2026/07/25 21:21 upstream 0ce37745d4bf 492bab15 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2026/07/24 07:06 upstream d326f83e819c 544adce9 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2026/07/22 03:44 upstream 248951ddc14d b561ce9c .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in ocfs2_xattr_set
2026/07/21 20:26 upstream b95f03f04d47 7c5de9c3 .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/07/19 15:40 linux-next cc2b5f627e8c 72524a66 .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.