[v6.1] WARNING in chown_common (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: da3c5173c55f Linux 6.1.140
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=114c7c82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=46e5b914cae7bc26
dashboard link: https://syzkaller.appspot.com/bug?extid=824e76f3321a45b18173
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f64777e3df5f/disk-da3c5173.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/86760acf06d3/vmlinux-da3c5173.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4b53296c1a0a/bzImage-da3c5173.xz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff8880509f1bc0, owner = 0x0, curr 0xffff88802f283b80, list empty
WARNING: CPU: 1 PID: 8027 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 1 PID: 8027 at kernel/locking/rwsem.c:1372 up_write+0x3a1/0x420 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 8027 Comm: syz.8.1298 Not tainted 6.1.140-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:__up_write kernel/locking/rwsem.c:1371 [inline]
RIP: 0010:up_write+0x3a1/0x420 kernel/locking/rwsem.c:1626
Code: 44 d0 48 c7 c7 80 f3 6b 8a 48 c7 c6 c0 f5 6b 8a 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 c3 88 ea ff 48 83 c4 08 <0f> 0b e9 6b fd ff ff 48 c7 c1 e8 b4 fe 8d 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90005f4fc50 EFLAGS: 00010296
RAX: cb918821375b0000 RBX: ffff8880509f1bc0 RCX: 0000000000080000
RDX: ffffc9000efeb000 RSI: 0000000000015098 RDI: 0000000000015099
RBP: dffffc0000000000 R08: dffffc0000000000 R09: fffff52000be9f19
R10: fffff52000be9f19 R11: 1ffff92000be9f18 R12: 0000000000000000
R13: ffff8880509f1c18 R14: ffff8880509f1bc0 R15: 1ffff1100a13e379
FS: 00007f999e1ff6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc443d71d60 CR3: 0000000066cd8000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:763 [inline]
chown_common+0x490/0x620 fs/open.c:738
do_fchownat+0x164/0x270 fs/open.c:767
__do_sys_fchownat fs/open.c:782 [inline]
__se_sys_fchownat fs/open.c:779 [inline]
__x64_sys_fchownat+0xb1/0xc0 fs/open.c:779
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f999e38e929
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:00007f999e1ff038 EFLAGS: 00000246 ORIG_RAX: 0000000000000104
RAX: ffffffffffffffda RBX: 00007f999e5b6080 RCX: 00007f999e38e929
RDX: 0000000000000000 RSI: 0000200000000000 RDI: ffffffffffffff9c
RBP: 00007f999e410ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f999e5b6080 R15: 00007ffeab9f95b8
</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

[syzbot]

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