[vfs?] WARNING in vfs_setxattr

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1f5abbd77e2c Merge tag 'thermal-6.2-rc3' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=158165a8480000
kernel config: https://syzkaller.appspot.com/x/.config?x=affadc28955d87c3
dashboard link: https://syzkaller.appspot.com/bug?extid=511bdcc82f0368e189bb
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/aa03e285dae7/disk-1f5abbd7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0fa3f456043f/vmlinux-1f5abbd7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/11a7c6fe5593/bzImage-1f5abbd7.xz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff8880896f7260, owner = 0x0, curr 0xffff888027f80140, list empty
WARNING: CPU: 0 PID: 9922 at kernel/locking/rwsem.c:1360 __up_write kernel/locking/rwsem.c:1360 [inline]
WARNING: CPU: 0 PID: 9922 at kernel/locking/rwsem.c:1360 up_write+0x429/0x520 kernel/locking/rwsem.c:1615
Modules linked in:
CPU: 0 PID: 9922 Comm: syz-executor.2 Not tainted 6.2.0-rc2-syzkaller-00203-g1f5abbd77e2c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:__up_write kernel/locking/rwsem.c:1360 [inline]
RIP: 0010:up_write+0x429/0x520 kernel/locking/rwsem.c:1615
Code: 3c 02 00 0f 85 da 00 00 00 48 8b 55 00 4d 89 f1 53 4d 89 f8 4c 89 e9 48 c7 c6 20 35 4c 8a 48 c7 c7 e0 32 4c 8a e8 5c f9 5c 08 <0f> 0b 59 e9 d9 fc ff ff 48 89 df e8 b7 c2 6b 00 e9 16 fc ff ff 48
RSP: 0000:ffffc9000702fab0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffffff8a4c3220 RCX: 0000000000000000
RDX: 0000000000040000 RSI: ffffffff8165927c RDI: fffff52000e05f48
RBP: ffff8880896f7260 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000000 R12: ffff8880896f7268
R13: ffff8880896f7260 R14: ffff888027f80140 R15: 0000000000000000
FS: 00007fc974107700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffee4640c78 CR3: 000000001eba1000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:761 [inline]
vfs_setxattr+0x14e/0x340 fs/xattr.c:325
do_setxattr+0x151/0x190 fs/xattr.c:608
setxattr+0x146/0x160 fs/xattr.c:631
path_setxattr+0x197/0x1c0 fs/xattr.c:650
__do_sys_setxattr fs/xattr.c:666 [inline]
__se_sys_setxattr fs/xattr.c:662 [inline]
__x64_sys_setxattr+0xc4/0x160 fs/xattr.c:662
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc97348c0c9
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:00007fc974107168 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fc9735ac050 RCX: 00007fc97348c0c9
RDX: 0000000000000000 RSI: 0000000020000040 RDI: 0000000020000000
RBP: 00007fc9734e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffec1349fef R14: 00007fc974107300 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.

[syzbot]

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