possible deadlock in ocfs2_xattr_set

Status: upstream: reported on 2024/09/25 09:02
Reported-by: syzbot+c0d46b51c54922dc038f@syzkaller.appspotmail.com
First crash: 688d, last: 18h42m
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 6d15h 699d 0/3 upstream: reported on 2024/09/14 01:11
upstream possible deadlock in ocfs2_xattr_set prio:high ocfs2 4 9335 1d08h 703d 0/29 upstream: reported on 2024/09/10 05:07
linux-6.6 possible deadlock in ocfs2_xattr_set 4 447 9d03h 421d 0/2 upstream: reported on 2025/06/19 18:15

Sample crash report:
JBD2: Ignoring recovery information on journal
jbd2_journal_bmap: journal block not found at offset 32 on loop0-75
JBD2: bad block at offset 32
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.19738/15610 is trying to acquire lock:
ffff8880500209c8 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
ffff8880500209c8 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2){+.+.}-{3:3}, at: ocfs2_xattr_set+0xbe4/0x1390 fs/ocfs2/xattr.c:3626

but task is already holding lock:
ffff888072995c78 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_xattr_set+0x491/0x1390 fs/ocfs2/xattr.c:3587

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&oi->ip_xattr_sem){++++}-{3:3}:
       down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
       ocfs2_init_acl+0x307/0x770 fs/ocfs2/acl.c:365
       ocfs2_mknod+0x18e0/0x2580 fs/ocfs2/namei.c:410
       ocfs2_create+0x1b6/0x4b0 fs/ocfs2/namei.c:674
       vfs_create+0x2db/0x460 fs/namei.c:3192
       do_mknodat+0x3a1/0x4d0 fs/namei.c:4043
       __do_sys_mknodat fs/namei.c:4071 [inline]
       __se_sys_mknodat fs/namei.c:4068 [inline]
       __x64_sys_mknodat+0xa5/0xc0 fs/namei.c:4068
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (jbd2_handle){++++}-{0:0}:
       jbd2_journal_lock_updates+0xa8/0x390 fs/jbd2/transaction.c:880
       __ocfs2_flush_truncate_log+0x2cf/0x1220 fs/ocfs2/alloc.c:6029
       ocfs2_flush_truncate_log fs/ocfs2/alloc.c:6076 [inline]
       ocfs2_truncate_log_shutdown+0x140/0x2f0 fs/ocfs2/alloc.c:6320
       ocfs2_dismount_volume+0x207/0x940 fs/ocfs2/super.c:1884
       generic_shutdown_super+0x130/0x340 fs/super.c:501
       kill_block_super+0x7c/0xe0 fs/super.c:1470
       deactivate_locked_super+0x93/0xf0 fs/super.c:332
       cleanup_mnt+0x471/0x4f0 fs/namespace.c:1191
       task_work_run+0x1d0/0x260 kernel/task_work.c:203
       resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
       exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
       exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210
       __syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
       syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
       do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3095 [inline]
       check_prevs_add kernel/locking/lockdep.c:3214 [inline]
       validate_chain kernel/locking/lockdep.c:3830 [inline]
       __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
       lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
       down_write+0x36/0x60 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:758 [inline]
       ocfs2_xattr_set+0xbe4/0x1390 fs/ocfs2/xattr.c:3626
       ocfs2_set_acl+0x4d4/0x580 fs/ocfs2/acl.c:254
       ocfs2_iop_set_acl+0x190/0x2b0 fs/ocfs2/acl.c:285
       set_posix_acl fs/posix_acl.c:1160 [inline]
       posix_acl_xattr_set+0x388/0x3f0 fs/posix_acl.c:1189
       __vfs_setxattr+0x3d8/0x410 fs/xattr.c:182
       __vfs_setxattr_noperm+0x126/0x5e0 fs/xattr.c:216
       vfs_setxattr+0x167/0x2e0 fs/xattr.c:309
       do_setxattr fs/xattr.c:594 [inline]
       setxattr+0x2a3/0x330 fs/xattr.c:617
       path_setxattr+0x147/0x290 fs/xattr.c:636
       __do_sys_setxattr fs/xattr.c:652 [inline]
       __se_sys_setxattr fs/xattr.c:648 [inline]
       __x64_sys_setxattr+0xb7/0xd0 fs/xattr.c:648
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

Chain exists of:
  &ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2 --> jbd2_handle --> &oi->ip_xattr_sem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&oi->ip_xattr_sem);
                               lock(jbd2_handle);
                               lock(&oi->ip_xattr_sem);
  lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#2);

 *** DEADLOCK ***

3 locks held by syz.0.19738/15610:
 #0: ffff8880782da460 (sb_writers#23){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402
 #1: ffff888072995f48 (&type->i_mutex_dir_key#30){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
 #1: ffff888072995f48 (&type->i_mutex_dir_key#30){+.+.}-{3:3}, at: vfs_setxattr+0x140/0x2e0 fs/xattr.c:308
 #2: ffff888072995c78 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_xattr_set+0x491/0x1390 fs/ocfs2/xattr.c:3587

stack backtrace:
CPU: 0 PID: 15610 Comm: syz.0.19738 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3095 [inline]
 check_prevs_add kernel/locking/lockdep.c:3214 [inline]
 validate_chain kernel/locking/lockdep.c:3830 [inline]
 __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
 down_write+0x36/0x60 kernel/locking/rwsem.c:1573
 inode_lock include/linux/fs.h:758 [inline]
 ocfs2_xattr_set+0xbe4/0x1390 fs/ocfs2/xattr.c:3626
 ocfs2_set_acl+0x4d4/0x580 fs/ocfs2/acl.c:254
 ocfs2_iop_set_acl+0x190/0x2b0 fs/ocfs2/acl.c:285
 set_posix_acl fs/posix_acl.c:1160 [inline]
 posix_acl_xattr_set+0x388/0x3f0 fs/posix_acl.c:1189
 __vfs_setxattr+0x3d8/0x410 fs/xattr.c:182
 __vfs_setxattr_noperm+0x126/0x5e0 fs/xattr.c:216
 vfs_setxattr+0x167/0x2e0 fs/xattr.c:309
 do_setxattr fs/xattr.c:594 [inline]
 setxattr+0x2a3/0x330 fs/xattr.c:617
 path_setxattr+0x147/0x290 fs/xattr.c:636
 __do_sys_setxattr fs/xattr.c:652 [inline]
 __se_sys_setxattr fs/xattr.c:648 [inline]
 __x64_sys_setxattr+0xb7/0xd0 fs/xattr.c:648
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f98aff9e0d9
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:00007f98ae1f6028 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f98b0225fa0 RCX: 00007f98aff9e0d9
RDX: 0000200000000100 RSI: 0000200000002a40 RDI: 0000200000002a00
RBP: 00007f98b0035024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000024 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f98b0226038 R14: 00007f98b0225fa0 R15: 00007fffd7cb5968
 </TASK>
OCFS2: ERROR (device loop0): 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.0.19738,15610,0):ocfs2_claim_suballoc_bits:2015 ERROR: status = -30
(syz.0.19738,15610,0):__ocfs2_claim_clusters:2387 ERROR: status = -30
(syz.0.19738,15610,0):__ocfs2_claim_clusters:2395 ERROR: status = -30
(syz.0.19738,15610,0):ocfs2_block_group_alloc_contig:455 ERROR: status = -30
(syz.0.19738,15610,0):ocfs2_block_group_alloc:727 ERROR: status = -30
(syz.0.19738,15610,0):ocfs2_block_group_alloc:780 ERROR: status = -30
(syz.0.19738,15610,0):ocfs2_reserve_suballoc_bits:855 ERROR: status = -30
(syz.0.19738,15610,0):ocfs2_reserve_suballoc_bits:872 ERROR: status = -30
(syz.0.19738,15610,0):ocfs2_reserve_new_metadata_blocks:1012 ERROR: status = -30
(syz.0.19738,15610,0):ocfs2_reserve_new_metadata_blocks:1035 ERROR: status = -30
(syz.0.19738,15610,0):ocfs2_init_xattr_set_ctxt:3284 ERROR: status = -30
(syz.0.19738,15610,0):ocfs2_xattr_set:3641 ERROR: status = -30

Crashes (919):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/12 02:07 linux-6.1.y e4f7d8be268e f8d35649 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/08/11 13:42 linux-6.1.y e4f7d8be268e 71790083 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/08/10 11:52 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/08/10 07:15 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/08/06 18:57 linux-6.1.y 03f3a99e8e93 c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/27 12:32 linux-6.1.y dc5c83b7f5f8 aae9036b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/20 11:25 linux-6.1.y 090666d3cc90 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/15 17:07 linux-6.1.y 090666d3cc90 a4ed0f4f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/14 15:56 linux-6.1.y 090666d3cc90 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/14 00:46 linux-6.1.y 090666d3cc90 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/10 18:47 linux-6.1.y 090666d3cc90 99e64375 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/09 21:40 linux-6.1.y 090666d3cc90 a0c310a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/09 10:18 linux-6.1.y 090666d3cc90 b9f1ceaa .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/07 00:42 linux-6.1.y 090666d3cc90 8e71ce95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/04 14:47 linux-6.1.y 090666d3cc90 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/03 21:50 linux-6.1.y fdb6fcb41cc7 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/02 17:19 linux-6.1.y fdb6fcb41cc7 2b70b115 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/07/02 17:14 linux-6.1.y fdb6fcb41cc7 2b70b115 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/06/30 02:56 linux-6.1.y fdb6fcb41cc7 fff8d0a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/06/25 05:39 linux-6.1.y fdb6fcb41cc7 cfa969bf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/06/23 04:00 linux-6.1.y fdb6fcb41cc7 5a630be6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/06/22 18:25 linux-6.1.y fdb6fcb41cc7 5a630be6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/06/18 11:08 linux-6.1.y 228da13e907e a776b0d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/06/17 23:15 linux-6.1.y 228da13e907e b62b3ded .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/06/16 04:35 linux-6.1.y 228da13e907e 50bb0618 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/06/12 17:02 linux-6.1.y 228da13e907e 1d2f3589 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2024/09/25 09:02 linux-6.1.y e526b12bf916 349a68c4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ocfs2_xattr_set
2026/08/14 05:20 linux-6.1.y e4f7d8be268e b13552fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/08/09 17:34 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/08/09 15:48 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/07/27 13:58 linux-6.1.y dc5c83b7f5f8 aae9036b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/07/12 18:52 linux-6.1.y 090666d3cc90 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/07/11 18:36 linux-6.1.y 090666d3cc90 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/07/11 16:42 linux-6.1.y 090666d3cc90 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/07/11 07:03 linux-6.1.y 090666d3cc90 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/07/10 15:38 linux-6.1.y 090666d3cc90 99e64375 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/07/10 05:29 linux-6.1.y 090666d3cc90 4167ee25 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/07/01 05:03 linux-6.1.y fdb6fcb41cc7 00a5cf1c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/30 12:34 linux-6.1.y fdb6fcb41cc7 fff8d0a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/30 03:59 linux-6.1.y fdb6fcb41cc7 fff8d0a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/28 09:27 linux-6.1.y fdb6fcb41cc7 fb92f11c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/24 01:33 linux-6.1.y fdb6fcb41cc7 042555ff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/23 13:46 linux-6.1.y fdb6fcb41cc7 4b1d8f01 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/22 20:06 linux-6.1.y fdb6fcb41cc7 5a630be6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/22 15:49 linux-6.1.y fdb6fcb41cc7 43bfcdb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/22 01:21 linux-6.1.y fdb6fcb41cc7 43bfcdb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/20 16:34 linux-6.1.y fdb6fcb41cc7 43bfcdb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/19 02:49 linux-6.1.y 228da13e907e a776b0d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/18 05:09 linux-6.1.y 228da13e907e b62b3ded .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
2026/06/14 20:27 linux-6.1.y 228da13e907e 1d2f3589 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ocfs2_xattr_set
* Struck through repros no longer work on HEAD.