Re: BUG: SMB3.11 POSIX extensions: Absolute symlinks lose leading slash on creation

On 6/26/26 5:39 PM, Max-Ulrich Farber wrote:
> Steps to reproduce:
> 1. Mount a Samba share on a Linux client with SMB3.11 and POSIX 
> extensions enabled.
> 2. Run the following command on the client:
>     ln -s /media/Raspi/Test/Reisen /media/Raspi/Reisen
> 
> Expected result:
> The symlink points to the absolute path:
> /media/Raspi/Reisen -> /media/Raspi/Test/Reisen
> 
> Actual result:
> The leading slash is missing, creating an invalid relative path:
> /media/Raspi/Reisen -> media/Raspi/Test/Reisen´
iirc this was intentionally done this way to aoid the dreaded symlink races.

Now that we store as empty file + xattr on the server, not real 
symlinks, this design decision might need to be revisited.

I don't remember of the top of my head if this behaviour is implemented 
in the client or the server. Does anyone remember? I'd have to check.

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEE+uLGCIokJSBRxVnkqh6bcSY5nkYFAmo+ucYFAwAAAAAACgkQqh6bcSY5nkas
URAAw4KYZ3YW4rz5tG0FINSo1CGPzfC2NTgiIZ8I68G5Po1dlNBGcKc7gHeThO0VECAXgPTtglDo
FF8h0jkyjdxZPrIOuG8T9+C6Q1Yi42XskdnVRnGQk39HrAIh2Q6QrlUeP0+JosRHNHiI7nSA+Mjc
5O9egY9PpPr4ydt+T5DRmYpsch6aB8PAf2NPUk1OFnp0PrJT3q0yug0BC5O9aDHo/kD2aS/7BAsI
GPWG/7K1eb/e4eVwnhBqEU4ytOgisCTRNTkzro8j9WsfajpTwzXuhyiJL+Lxg5lgBXDp9CrdDJ8U
nO0BmVuDbuuHBZe0AaShgJONWtV2buiUdJlWQ9llwUbyzqBOGaHiaAAZ8kxuLZAldT/629JqGVfr
brzKd7oqzO7hIi+FkI+boBr6ZN59mE8t1ip9S0NkQeDO1EyOmvVsV/bOxTcA08ABCr/q3TcFXUpc
PkR9gVVfrDqm35Fho0KO3HHBNT1+dX0NqmSz5jv5H2gFpFjOR3GYS50Fx7H2CjB6nmykiOy9FDrd
bo+f9/FijahJ5rkgMxYWtyITI+Uvvuv5oJ5UkFqgb5AyUpT1KzwvV2ruiRCV8QH+uSL97IPtVauT
uX4m0eWIaUyxEeBSnm9X6GY+rpWvT1u00LcxGLUMs9J7M5F1Q4EvmYjFYhin1S35uFV8GZtvZwMR
TY0=
=nH0E
-----END PGP SIGNATURE-----