[v6.6] WARNING in ocfs2_trim_fs_lock_res_init (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5fa4793a2d2d Linux 6.6.119
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1203e77c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=691a6769a86ac817
dashboard link: https://syzkaller.appspot.com/bug?extid=8be863e9cfecb2c648d7
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63699875f1dd/disk-5fa4793a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8506652fcb6f/vmlinux-5fa4793a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b30ceed1710/bzImage-5fa4793a.xz

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

(syz.0.1812,17919,1):ocfs2_block_check_validate:402 ERROR: CRC32 failed: stored: 0xb3775c19, computed 0x2dd1c265. Applying ECC.
ocfs2: Readonly device (7,0) detected. Cluster services will not be used for this mount. Recovery will be skipped.
ocfs2: Mounting device (7,0) on (node local, slot 65535) with ordered data mode.
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 1 PID: 17919 at kernel/locking/mutex.c:582 __mutex_lock_common kernel/locking/mutex.c:582 [inline]
WARNING: CPU: 1 PID: 17919 at kernel/locking/mutex.c:582 __mutex_lock+0xb8c/0xcc0 kernel/locking/mutex.c:747
Modules linked in:
CPU: 1 PID: 17919 Comm: syz.0.1812 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:582 [inline]
RIP: 0010:__mutex_lock+0xb8c/0xcc0 kernel/locking/mutex.c:747
Code: 04 08 84 c0 0f 85 20 01 00 00 83 3d 9d 38 da 03 00 0f 85 81 f5 ff ff 48 c7 c7 80 a7 aa 8a 48 c7 c6 20 a8 aa 8a e8 84 ef df f6 <0f> 0b e9 67 f5 ff ff 0f 0b e9 47 f9 ff ff 0f 0b e9 ff f5 ff ff 48
RSP: 0018:ffffc900044c77e0 EFLAGS: 00010246
RAX: 43c3c40b5ba50600 RBX: ffff88806a174df0 RCX: 0000000000080000
RDX: ffffc9000ce22000 RSI: 0000000000001dd8 RDI: 0000000000001dd9
RBP: ffffc900044c7940 R08: ffff8880b8f28c13 R09: 1ffff110171e5182
R10: dffffc0000000000 R11: ffffed10171e5183 R12: 0000000000000000
R13: 1ffff92000898f0c R14: dffffc0000000000 R15: 0000000000000000
FS: 00007f02eead46c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055928f3ba950 CR3: 000000005025c000 CR4: 00000000003506e0
Call Trace:
<TASK>
ocfs2_trim_fs_lock_res_init+0x33/0x1c0 fs/ocfs2/dlmglue.c:702
ocfs2_trim_fs+0x12a/0x22d0 fs/ocfs2/alloc.c:7663
ocfs2_ioctl+0x694/0x750 fs/ocfs2/ioctl.c:935
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f02edb8f749
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:00007f02eead4038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f02edde5fa0 RCX: 00007f02edb8f749
RDX: 0000200000000080 RSI: 00000000c0185879 RDI: 0000000000000005
RBP: 00007f02edc13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f02edde6038 R14: 00007f02edde5fa0 R15: 00007ffd7ec61fe8
</TASK>


---
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 syzk...@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 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