[v6.1] WARNING in chmod_common

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4078fa637fcd Linux 6.1.91
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13e94d58980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1d51cd200f88f60
dashboard link: https://syzkaller.appspot.com/bug?extid=b08ff8d057d24b5cd0d8
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b1a0a011a73e/disk-4078fa63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cfaef39014a6/vmlinux-4078fa63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/36e61b51fbe2/Image-4078fa63.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000f3c81950, owner = 0x0, curr 0xffff0000cf950000, list empty
WARNING: CPU: 0 PID: 11179 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 0 PID: 11179 at kernel/locking/rwsem.c:1372 up_write+0x5c4/0x76c kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 11179 Comm: syz-executor.1 Not tainted 6.1.91-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
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 : ffff80001f1c7a60
x29: ffff80001f1c7ae0 x28: ffff0000cf950000 x27: 1fffe0001e790337
x26: dfff800000000000 x25: 1fffe0001e79032b x24: ffff0000f3c819a8
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000cf950000
x20: ffff0000f3c81950 x19: ffff0000f3c81950 x18: 1fffe0003686af76
x17: ffff80001584d000 x16: ffff800008305e40 x15: ffff0001b4357bbc
x14: 1ffff00002b0a0b0 x13: dfff800000000000 x12: 0000000000000003
x11: 0000000000ff0100 x10: 0000000000000003 x9 : 548b9d577234a200
x8 : 548b9d577234a200 x7 : ffff80000827c88c x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff8000122bc6e0 x0 : ffff80019ebb5000
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]
chmod_common+0x248/0x418 fs/open.c:609
do_fchmodat fs/open.c:645 [inline]
__do_sys_fchmodat fs/open.c:658 [inline]
__se_sys_fchmodat fs/open.c:655 [inline]
__arm64_sys_fchmodat+0x118/0x1dc fs/open.c:655
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
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: 296
hardirqs last enabled at (295): [<ffff80000827c92c>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1366 [inline]
hardirqs last enabled at (295): [<ffff80000827c92c>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:5004
hardirqs last disabled at (296): [<ffff80001215b3cc>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (288): [<ffff800008020d7c>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (288): [<ffff800008020d7c>] __do_softirq+0xc1c/0xe38 kernel/softirq.c:600
softirqs last disabled at (279): [<ffff80000802a99c>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:80
---[ 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