[v6.6] WARNING in do_symlinkat

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cbb31f77b879 Linux 6.6.121
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10cd7f9a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2a950bf7c0bff9f9
dashboard link: https://syzkaller.appspot.com/bug?extid=80f3ff4f779933fea398
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6436cbae3604/disk-cbb31f77.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8f3a3d318f99/vmlinux-cbb31f77.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84920a2a012f/bzImage-cbb31f77.xz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888077e69bd0, owner = 0x0, curr 0xffff88802d9a3c00, list empty
WARNING: CPU: 0 PID: 6663 at kernel/locking/rwsem.c:1370 __up_write kernel/locking/rwsem.c:1369 [inline]
WARNING: CPU: 0 PID: 6663 at kernel/locking/rwsem.c:1370 up_write+0x393/0x410 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 0 PID: 6663 Comm: syz.3.154 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:__up_write kernel/locking/rwsem.c:1369 [inline]
RIP: 0010:up_write+0x393/0x410 kernel/locking/rwsem.c:1626
Code: 44 d0 48 c7 c7 a0 bc ca 8a 48 c7 c6 e0 be ca 8a 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 71 43 e9 ff 48 83 c4 08 <0f> 0b e9 7d fd ff ff 48 c7 c1 b0 0e 8b 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc9000bd37df0 EFLAGS: 00010296
RAX: 7400976bad529a00 RBX: ffff888077e69bd0 RCX: 0000000000080000
RDX: ffffc900107b3000 RSI: 0000000000022e14 RDI: 0000000000022e15
RBP: dffffc0000000000 R08: ffffc9000bd379e7 R09: 1ffff920017a6f3c
R10: dffffc0000000000 R11: fffff520017a6f3d R12: 0000000000000000
R13: ffff888077e69c28 R14: ffff888077e69bd0 R15: 1ffff1100efcd37b
FS: 00007f240939a6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f24085e8400 CR3: 000000005cc1f000 CR4: 00000000003506f0
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:809 [inline]
done_path_create fs/namei.c:3941 [inline]
do_symlinkat+0x1fa/0x400 fs/namei.c:4509
__do_sys_symlink fs/namei.c:4528 [inline]
__se_sys_symlink fs/namei.c:4526 [inline]
__x64_sys_symlink+0x7e/0x90 fs/namei.c:4526
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f240859acb9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f240939a028 EFLAGS: 00000246 ORIG_RAX: 0000000000000058
RAX: ffffffffffffffda RBX: 00007f2408816270 RCX: 00007f240859acb9
RDX: 0000000000000000 RSI: 0000200000001300 RDI: 00002000000012c0
RBP: 00007f2408608bf7 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2408816308 R14: 00007f2408816270 R15: 00007fff19a12208
</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