[v5.15] WARNING in do_symlinkat (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b911329317b4 Linux 5.15.133
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=114c8f21680000
kernel config: https://syzkaller.appspot.com/x/.config?x=a9c9f0083f439f72
dashboard link: https://syzkaller.appspot.com/bug?extid=cba2e1e7c98e2bcd7619
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/46530025981a/disk-b9113293.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d27830145a50/vmlinux-b9113293.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee1d0b88a1d9/bzImage-b9113293.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888080e96310, owner = 0x0, curr 0xffff888021651dc0, list empty
WARNING: CPU: 1 PID: 11905 at kernel/locking/rwsem.c:1342 __up_write kernel/locking/rwsem.c:1341 [inline]
WARNING: CPU: 1 PID: 11905 at kernel/locking/rwsem.c:1342 up_write+0x473/0x4d0 kernel/locking/rwsem.c:1594
Modules linked in:
CPU: 1 PID: 11905 Comm: syz-executor.4 Not tainted 5.15.133-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/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 ff 8a 8a 48 c7 c6 a0 02 8b 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 41 14 ea ff 48 83 c4 08 <0f> 0b e9 86 fd ff ff 48 c7 c1 08 40 e4 8d 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc900030cfd40 EFLAGS: 00010292
RAX: e568f550f7ad3100 RBX: ffffffff8a8b00c0 RCX: 0000000000040000
RDX: ffffc90005d79000 RSI: 000000000003df8c RDI: 000000000003df8d
RBP: ffffc900030cfe10 R08: ffffffff816658bc R09: ffffed10173667a8
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff888080e96310 R14: 1ffff92000619fb0 R15: dffffc0000000000
FS: 00007fa1e29e76c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30726000 CR3: 0000000063b98000 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]
done_path_create fs/namei.c:3815 [inline]
do_symlinkat+0x25a/0x600 fs/namei.c:4390
__do_sys_symlinkat fs/namei.c:4404 [inline]
__se_sys_symlinkat fs/namei.c:4401 [inline]
__x64_sys_symlinkat+0x95/0xa0 fs/namei.c:4401
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:0x7fa1ec686ae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa1e29e70c8 EFLAGS: 00000246 ORIG_RAX: 000000000000010a
RAX: ffffffffffffffda RBX: 00007fa1ec7a6050 RCX: 00007fa1ec686ae9
RDX: 0000000020000080 RSI: 0000000000000004 RDI: 0000000020000000
RBP: 00007fa1ec6d247a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fa1ec7a6050 R15: 00007ffebae5d5b8
</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 overwrite 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]

syzbot has found a reproducer for the following issue on:

HEAD commit: b911329317b4 Linux 5.15.133
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=13b8aeb2680000

kernel config: https://syzkaller.appspot.com/x/.config?x=a9c9f0083f439f72
dashboard link: https://syzkaller.appspot.com/bug?extid=cba2e1e7c98e2bcd7619
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a6738a680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/46530025981a/disk-b9113293.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d27830145a50/vmlinux-b9113293.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee1d0b88a1d9/bzImage-b9113293.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/642946655a49/mount_0.gz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888071219950, owner = 0x0, curr 0xffff888023135940, list empty
WARNING: CPU: 1 PID: 4182 at kernel/locking/rwsem.c:1342 __up_write kernel/locking/rwsem.c:1341 [inline]
WARNING: CPU: 1 PID: 4182 at kernel/locking/rwsem.c:1342 up_write+0x473/0x4d0 kernel/locking/rwsem.c:1594
Modules linked in:
CPU: 1 PID: 4182 Comm: syz-executor.2 Not tainted 5.15.133-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/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 ff 8a 8a 48 c7 c6 a0 02 8b 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 41 14 ea ff 48 83 c4 08 <0f> 0b e9 86 fd ff ff 48 c7 c1 08 40 e4 8d 80 e1 07 80 c1 03 38 c1

RSP: 0018:ffffc90005d17d40 EFLAGS: 00010292
RAX: 8cebdde5fdbb6a00 RBX: ffffffff8a8b00c0 RCX: ffff888023135940
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90005d17e10 R08: ffffffff816658bc R09: ffffed1017364f24

R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000

R13: ffff888071219950 R14: 1ffff92000ba2fb0 R15: dffffc0000000000
FS: 00007fda5b8796c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 0000555556c21938 CR3: 0000000070da1000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:792 [inline]
done_path_create fs/namei.c:3815 [inline]
do_symlinkat+0x25a/0x600 fs/namei.c:4390
__do_sys_symlinkat fs/namei.c:4404 [inline]
__se_sys_symlinkat fs/namei.c:4401 [inline]
__x64_sys_symlinkat+0x95/0xa0 fs/namei.c:4401
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:0x7fda64718ae9

Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007fda5b8790c8 EFLAGS: 00000246 ORIG_RAX: 000000000000010a
RAX: ffffffffffffffda RBX: 00007fda64838050 RCX: 00007fda64718ae9

RDX: 0000000020000080 RSI: 0000000000000004 RDI: 0000000020000000

RBP: 00007fda6476447a R08: 0000000000000000 R09: 0000000000000000

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000

R13: 000000000000006e R14: 00007fda64838050 R15: 00007fff09333a98
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.