[v5.15] WARNING: locking bug in ocfs2_inode_lock_full_nested (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c86c4726e7f0 Linux 5.15.211
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12580ab9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f8e2266b61925dc
dashboard link: https://syzkaller.appspot.com/bug?extid=ff207c426d60bf67f1c4
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c3e980557785/disk-c86c4726.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5fbaf3714ad0/vmlinux-c86c4726.xz
kernel image: https://storage.googleapis.com/syzbot-assets/de60a4f1e940/bzImage-c86c4726.xz

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

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 0 PID: 8177 at kernel/locking/lockdep.c:201 hlock_class kernel/locking/lockdep.c:-1 [inline]
WARNING: CPU: 0 PID: 8177 at kernel/locking/lockdep.c:201 check_wait_context kernel/locking/lockdep.c:4686 [inline]
WARNING: CPU: 0 PID: 8177 at kernel/locking/lockdep.c:201 __lock_acquire+0x7dc/0x7b50 kernel/locking/lockdep.c:4962
Modules linked in:
CPU: 0 PID: 8177 Comm: syz.4.874 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/25/2026
RIP: 0010:hlock_class kernel/locking/lockdep.c:201 [inline]
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4686 [inline]
RIP: 0010:__lock_acquire+0x7dc/0x7b50 kernel/locking/lockdep.c:4962
Code: 83 3d 7f 39 2e 0c 00 0f 85 d3 fd ff ff 48 c7 c7 80 2a 2b 8a 48 c7 c6 20 2d 2b 8a e8 ae 44 57 08 48 ba 00 00 00 00 00 fc ff df <0f> 0b e9 af fd ff ff e8 98 08 88 02 85 c0 0f 84 79 0a 00 00 48 c7
RSP: 0018:ffffc90004ed75e0 EFLAGS: 00010046
RAX: 5d54349c88b62900 RBX: 0000000000001696 RCX: 0000000000080000
RDX: dffffc0000000000 RSI: 00000000000033f1 RDI: 00000000000033f2
RBP: ffffc90004ed7810 R08: ffff8880b902795b R09: 1ffff11017204f2b
R10: dffffc0000000000 R11: ffffed1017204f2c R12: ffff88802ab828f8
R13: ffff88802ab81dc0 R14: 0000000000000000 R15: ffff88802ab828d8
FS: 00007fac12ed96c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f65a3ca5000 CR3: 0000000075959000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:364 [inline]
ocfs2_is_hard_readonly fs/ocfs2/ocfs2.h:639 [inline]
ocfs2_inode_lock_full_nested+0x121/0x1b10 fs/ocfs2/dlmglue.c:2443
ocfs2_inode_lock_tracker+0x1cc/0x700 fs/ocfs2/dlmglue.c:2690
ocfs2_permission+0xc3/0x1e0 fs/ocfs2/file.c:1352
do_inode_permission fs/namei.c:459 [inline]
inode_permission+0x239/0x480 fs/namei.c:526
vfs_truncate+0x168/0x2f0 fs/open.c:89
do_sys_truncate+0xf2/0x1c0 fs/open.c:134
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fac14c80e99
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:00007fac12ed9028 EFLAGS: 00000246
ORIG_RAX: 000000000000004c
RAX: ffffffffffffffda RBX: 00007fac14f08fa0 RCX: 00007fac14c80e99
RDX: 0000000000000000 RSI: 0000000000f0ffff RDI: 0000200000000000
RBP: 00007fac14d16eaf R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fac14f09038 R14: 00007fac14f08fa0 R15: 00007ffd217333a8
</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