[syzbot] [ocfs2?] WARNING in ocfs2_xa_remove_entry

[syzbot <syzbot+8021f90e085c9ef5797d@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    187d0801404f Merge tag 'libcrypto-fixes-for-linus' of git:..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11803e1a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=de48dccdf203ea90
dashboard link: https://syzkaller.appspot.com/bug?extid=8021f90e085c9ef5797d
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15803e1a580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13c671c2580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-187d0801.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/48c184ec5db6/vmlinux-187d0801.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3eafabbccdb7/bzImage-187d0801.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/d5c016f0013c/mount_0.gz
  fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=15c671c2580000)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8021f90e085c9ef5797d@syzkaller.appspotmail.com

JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
------------[ cut here ]------------
memmove: detected buffer overflow: 16 byte read of buffer size 0
WARNING: lib/string_helpers.c:1036 at 0x0, CPU#0: syz.0.17/5492
Modules linked in:
CPU: 0 UID: 0 PID: 5492 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:__fortify_report+0x89/0xa0 lib/string_helpers.c:1035
Code: e8 bc db 98 fd 48 8d 3d 85 b5 1b 0b 45 84 e4 49 8b 37 48 c7 c0 00 e5 df 8b 48 c7 c1 20 e5 df 8b 48 0f 44 c8 4c 89 f2 49 89 d8 <67> 48 0f b9 3a 5b 41 5c 41 5e 41 5f 5d e9 15 6a cf 06 cc cc cc cc
RSP: 0018:ffffc90002a2edb8 EFLAGS: 00010246
RAX: ffffffff8bdfe500 RBX: 0000000000000000 RCX: ffffffff8bdfe500
RDX: 0000000000000010 RSI: ffffffff8bdfe400 RDI: ffffffff8fac76a0
RBP: 0000000000000012 R08: 0000000000000000 R09: 0000000000000004
R10: ffff888056e9738c R11: ffffed100add2e7a R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000010 R15: ffffffff8bdfe208
FS:  00005555818de500(0000) GS:ffff88808d22f000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000111ed000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 __fortify_panic+0x9/0x10 lib/string_helpers.c:1042
 fortify_memcpy_chk include/linux/fortify-string.h:599 [inline]
 ocfs2_xa_remove_entry+0x304/0x3e0 fs/ocfs2/xattr.c:1955
 ocfs2_xa_remove fs/ocfs2/xattr.c:2043 [inline]
 ocfs2_xa_set+0xaf4/0x2a70 fs/ocfs2/xattr.c:2247
 ocfs2_xattr_block_set+0x3ca/0x31b0 fs/ocfs2/xattr.c:2985
 __ocfs2_xattr_set_handle+0x27e/0xf20 fs/ocfs2/xattr.c:-1
 ocfs2_xattr_set+0xde8/0x11f0 fs/ocfs2/xattr.c:3650
 __vfs_removexattr+0x431/0x470 fs/xattr.c:518
 __vfs_removexattr_locked+0x1e8/0x230 fs/xattr.c:553
 vfs_removexattr+0x80/0x1b0 fs/xattr.c:575
 removexattr fs/xattr.c:1023 [inline]
 filename_removexattr fs/xattr.c:1052 [inline]
 path_removexattrat+0x35d/0x690 fs/xattr.c:1088
 __do_sys_lremovexattr fs/xattr.c:1106 [inline]
 __se_sys_lremovexattr fs/xattr.c:1103 [inline]
 __x64_sys_lremovexattr+0x65/0x80 fs/xattr.c:1103
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7efe82f8f7c9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc19a71458 EFLAGS: 00000246 ORIG_RAX: 00000000000000c6
RAX: ffffffffffffffda RBX: 00007efe831e5fa0 RCX: 00007efe82f8f7c9
RDX: 0000000000000000 RSI: 0000200000000180 RDI: 00002000000000c0
RBP: 00007efe83013f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007efe831e5fa0 R14: 00007efe831e5fa0 R15: 0000000000000002
 </TASK>
----------------
Code disassembly (best guess):
   0:	e8 bc db 98 fd       	call   0xfd98dbc1
   5:	48 8d 3d 85 b5 1b 0b 	lea    0xb1bb585(%rip),%rdi        # 0xb1bb591
   c:	45 84 e4             	test   %r12b,%r12b
   f:	49 8b 37             	mov    (%r15),%rsi
  12:	48 c7 c0 00 e5 df 8b 	mov    $0xffffffff8bdfe500,%rax
  19:	48 c7 c1 20 e5 df 8b 	mov    $0xffffffff8bdfe520,%rcx
  20:	48 0f 44 c8          	cmove  %rax,%rcx
  24:	4c 89 f2             	mov    %r14,%rdx
  27:	49 89 d8             	mov    %rbx,%r8
* 2a:	67 48 0f b9 3a       	ud1    (%edx),%rdi <-- trapping instruction
  2f:	5b                   	pop    %rbx
  30:	41 5c                	pop    %r12
  32:	41 5e                	pop    %r14
  34:	41 5f                	pop    %r15
  36:	5d                   	pop    %rbp
  37:	e9 15 6a cf 06       	jmp    0x6cf6a51
  3c:	cc                   	int3
  3d:	cc                   	int3
  3e:	cc                   	int3
  3f:	cc                   	int3


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup