[v5.15] WARNING in __generic_file_fsync

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8a7f2a5c5aa1 Linux 5.15.110
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1434da12280000
kernel config: https://syzkaller.appspot.com/x/.config?x=ba8d5c9d6c5289f
dashboard link: https://syzkaller.appspot.com/bug?extid=277c70e345c0122dc672
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fc04f54c047f/disk-8a7f2a5c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6b4ba4cb1191/vmlinux-8a7f2a5c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d927dc3f9670/bzImage-8a7f2a5c.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff88803911a810, owner = 0x0, curr 0xffff8880398a1d00, list empty
WARNING: CPU: 1 PID: 11184 at kernel/locking/rwsem.c:1342 __up_write kernel/locking/rwsem.c:1341 [inline]
WARNING: CPU: 1 PID: 11184 at kernel/locking/rwsem.c:1342 up_write+0x473/0x4d0 kernel/locking/rwsem.c:1594
Modules linked in:
CPU: 1 PID: 11184 Comm: syz-executor.1 Not tainted 5.15.110-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:__up_write kernel/locking/rwsem.c:1341 [inline]
RIP: 0010:up_write+0x473/0x4d0 kernel/locking/rwsem.c:1594
Code: 48 c7 c7 e0 ee 8a 8a 48 c7 c6 a0 f1 8a 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 c1 12 ea ff 48 83 c4 08 <0f> 0b e9 86 fd ff ff 48 c7 c1 08 d6 e3 8d 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc9000304fda0 EFLAGS: 00010296
RAX: 19f0184284140d00 RBX: ffffffff8a8aefc0 RCX: 0000000000040000
RDX: ffffc900038b1000 RSI: 000000000001665b RDI: 000000000001665c
RBP: ffffc9000304fe78 R08: ffffffff8166344c R09: ffffed10173667a0
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff88803911a810 R14: 1ffff92000609fbc R15: dffffc0000000000
FS: 00007f1e3a2cd700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e825000 CR3: 000000008c7dc000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:792 [inline]
__generic_file_fsync+0x159/0x190 fs/libfs.c:1120
generic_file_fsync+0x6f/0xe0 fs/libfs.c:1145
vfs_fsync_range fs/sync.c:188 [inline]
vfs_fsync fs/sync.c:202 [inline]
do_fsync fs/sync.c:212 [inline]
__do_sys_fdatasync fs/sync.c:225 [inline]
__se_sys_fdatasync fs/sync.c:223 [inline]
__x64_sys_fdatasync+0xb1/0x100 fs/sync.c:223
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1e43f7c169
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f1e3a2cd168 EFLAGS: 00000246 ORIG_RAX: 000000000000004b
RAX: ffffffffffffffda RBX: 00007f1e4409c050 RCX: 00007f1e43f7c169
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007f1e43fd7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffddc25465f R14: 00007f1e3a2cd300 R15: 0000000000022000
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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.