[v6.1] WARNING in path_openat (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 420102835862 Linux 6.1.134
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1639f4cc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b6a16d457784cab
dashboard link: https://syzkaller.appspot.com/bug?extid=31d11bcfaa8ae37872eb
compiler: Debian clang version 15.0.6, Debian LLD 15.0.6
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ebd558063376/disk-42010283.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8fddad580749/vmlinux-42010283.xz
kernel image: https://storage.googleapis.com/syzbot-assets/557917aaa3df/Image-42010283.gz.xz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000f59f91f0, owner = 0x0, curr 0xffff0000f63f9bc0, list empty
WARNING: CPU: 0 PID: 4861 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 0 PID: 4861 at kernel/locking/rwsem.c:1372 up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 4861 Comm: syz.3.128 Not tainted 6.1.134-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1371 [inline]
pc : up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
lr : __up_write kernel/locking/rwsem.c:1371 [inline]
lr : up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
sp : ffff8000216e7660
x29: ffff8000216e76e0 x28: ffff0000df910a48 x27: 1fffe0001eb3f24b
x26: dfff800000000000 x25: 1fffe0001eb3f23f x24: ffff0000f59f9248
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000f63f9bc0
x20: ffff0000f59f91f0 x19: ffff0000f59f91f0 x18: 1fffe00036798976
x17: ffff800015aed000 x16: ffff800008302888 x15: ffff0001b3cc4bbc
x14: 1ffff00002b5e0b2 x13: dfff800000000000 x12: 0000000000000003
x11: 0000000000ff0100 x10: 0000000000000003 x9 : 763bdb367355fc00
x8 : 763bdb367355fc00 x7 : ffff800008279464 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff80001247e5c0 x0 : ffff80019e280000
Call trace:
__up_write kernel/locking/rwsem.c:1371 [inline]
up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
inode_unlock include/linux/fs.h:763 [inline]
open_last_lookups fs/namei.c:3554 [inline]
path_openat+0x1158/0x2548 fs/namei.c:3780
do_filp_open+0x1bc/0x3cc fs/namei.c:3810
do_sys_openat2+0x128/0x3e0 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+0x1f0/0x240 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/0x168 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: 384
hardirqs last enabled at (383): [<ffff800008279504>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1367 [inline]
hardirqs last enabled at (383): [<ffff800008279504>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:5003
hardirqs last disabled at (384): [<ffff80001231a92c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (376): [<ffff8000081c40ac>] softirq_handle_end kernel/softirq.c:421 [inline]
softirqs last enabled at (376): [<ffff8000081c40ac>] handle_softirqs+0xb84/0xd58 kernel/softirq.c:606
softirqs last disabled at (363): [<ffff800008020174>] __do_softirq+0x14/0x20 kernel/softirq.c:612
---[ 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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.