[v6.1] WARNING in path_openat (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 363a599da6d9 Linux 6.1.153
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16f860e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=68aa5a3af1cb953a
dashboard link: https://syzkaller.appspot.com/bug?extid=c384b4b66951788282e7
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b29518096962/disk-363a599d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8196e10b1ead/vmlinux-363a599d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d3123d59503a/Image-363a599d.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000e286f1d0, owner = 0x0, curr 0xffff0000dc4ad340, list empty
WARNING: CPU: 0 PID: 5144 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 0 PID: 5144 at kernel/locking/rwsem.c:1372 up_write+0x494/0x5c0 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 5144 Comm: syz.3.108 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 62400005 (nZCv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1371 [inline]
pc : up_write+0x494/0x5c0 kernel/locking/rwsem.c:1626
lr : __up_write kernel/locking/rwsem.c:1371 [inline]
lr : up_write+0x494/0x5c0 kernel/locking/rwsem.c:1626
sp : ffff8000228077a0
x29: ffff8000228077b0 x28: ffff0000e2b70000 x27: ffff800022807ab8
x26: dfff800000000000 x25: 1fffe0001c50de47 x24: ffff0000e286f228
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000dc4ad340
x20: ffff0000e286f1d0 x19: ffff0000e286f1d0 x18: ffff800011abbcc0
x17: 1fffe00033ed797e x16: ffff8000082d22e0 x15: 0000000040000000
x14: 0000000000000002 x13: 1ffff00002a180b1 x12: 0000000000ff0100
x11: ff0080000a893b54 x10: 0000000000000003 x9 : d7424d694e4c6600
x8 : d7424d694e4c6600 x7 : ffff800008251e10 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff800011abd7c0 x0 : ffff80018a6a7000
Call trace:
__up_write kernel/locking/rwsem.c:1371 [inline]
up_write+0x494/0x5c0 kernel/locking/rwsem.c:1626
inode_unlock include/linux/fs.h:763 [inline]
open_last_lookups fs/namei.c:3554 [inline]
path_openat+0xe04/0x2680 fs/namei.c:3780
do_filp_open+0x174/0x344 fs/namei.c:3810
do_sys_openat2+0x128/0x3d8 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__arm64_sys_openat+0x120/0x154 fs/open.c:1345
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 306
hardirqs last enabled at (305): [<ffff800008251ea4>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1367 [inline]
hardirqs last enabled at (305): [<ffff800008251ea4>] finish_lock_switch+0xb0/0x1c4 kernel/sched/core.c:5003
hardirqs last disabled at (306): [<ffff800011958980>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (106): [<ffff80000803092c>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (104): [<ffff8000080308f8>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---


---
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