Re: BUG: SMB3.11 POSIX extensions: Absolute symlinks lose leading slash on creation
Ralph Boehme <[email protected]>
| Newsgroups | org.kernel.vger.linux-cifs |
|---|---|
| Message-ID | <[email protected]> |
On 6/26/26 7:41 PM, Ralph Boehme wrote: > 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. it's the client: in cifs_convert_path_to_utf16() it strips the leading slash for the symlink target when called from create_native_symlink(). As symlinks in SMB3 POSIX may be created any way the server thinks is safe (Samba does file+xattr, it never creates real symlinks on the server), so symlinks are just a client side thing and we should allow creating absolute symlinks. POSIX allows it (and users use it), so we should (safely) also allow it in SMB3 POSIX.
OpenPGP_signature.asc
(application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEE+uLGCIokJSBRxVnkqh6bcSY5nkYFAmo+wRsFAwAAAAAACgkQqh6bcSY5nkZF Mw//Sx2zkrCnG607809x0KdsypvA7plaqWUTWlnazhljHtxA09XkpTb2MN0AYYohnGqNt0up2OXV TLt8+XifBpqlyj/UMB76wTKnREnumWynd+BJDfxyPi2UgsZI7kIZ/ZrTzgbj7hZnLzpSlw5ZjRsx 1l5Lj6LGyKzN4mM+ZGPmTYiOwtW7L6xt4RtGTUk6FRPWPavmaQHCEL3M/LjRJU7+DUYCoGR3NUeo ImxBCm3ZXZF2ntB+3354XrBtB3Q0rHTRkU3zX6kyYlEiRV82I10ME30Az6Z8bEeNNAy+BtLyHv5g IPWN7hHlSkbJq4zVS5HmD7Bts1+7qKfM/LBz7N/e14jOnSrc6euKIOO/PEkSdhHyDcWQZabDFq1I nBpcTXjVmF3gs5K7aIEyRwvZqCezUGsDJ21qn+ushjFYg+Ej2alFg5omBYafMGiyZCB+3Nm9TyWl nksBDILLJrUDeaE9kEROZgAPtohsiwV736+uCug5gIHhrTGUcneVFFBGEwj4RRHUs9jU7K90QT8N OmHmWIvyAoPkiPWLhn+bCGvKSTWJslQnVw9V0JDkldzoiGZRhvjg2bOtAxjTbfRldji0SxBZucES HKSwhGsdpzc2vpakAqKLs+QAZ1gA6UpHWWbowoScpSFSV48YMOXPaYiKaO8Y/53Q38LAdDKADQOZ YcA= =qtXM -----END PGP SIGNATURE-----