Path not available in symbolic link

[sganis]

Bug Report

Symbolic links to full path folders produce an error of path unavailable.

How to Reproduce

Create a symbolic link in your home directory pointing to a full path folder, for example /home/support/lib -> /usr/lib:

$ cd
$ ln -s /usr/lib lib

From windows, mount the remote root path to Z: using golddrive or sshfs, open Explorer and go to an internal folder of that link, for example : Z:\home\support\lib\apt, this works. Then click the lib folder in the address bar, and the error occurs with folder unavailable:

Apparently the link target is not resolved correctly, it is resolving /home/support/usr/lib and it should be /usr/lib.
Double clicking every folder one at the time in the file browser works ok. The problem is when clicking the link in the address bar.

If the link is pointing to a relative path for example /home/support/lib2 -> ../../usr/lib, it works fine, this issue only occurs when the link is pointing to a full path.

Environment

• OS version: Windows 10
• WinFsp version: 1.10.22006 and later, it works in 1.9.21096 and older
• Linux: any Linux, issue found in WSL, RedHat and Ubuntu

[billziss-gh]

Does this problem happen if you mount with the relpath FUSE option?

[sganis]

You mean rellinks?
I am using this option.