Re: [RFC PATCH v2 6/9] ksmbd: support security.capability EAs
Ralph Boehme <[email protected]> Mon, 20 Jul 2026 08:57:42 +0200
| Newsgroups | org.kernel.vger.linux-cifs,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 7/17/26 5:39 AM, Ze Tan wrote:
> +static bool ksmbd_is_posix_ea_name(const char *name, size_t name_len)
> +{
> + if (ksmbd_is_security_capability_ea_name(name, name_len))
> + return true;
> +
> + return false;
> +}
> +
> +static int ksmbd_map_ea_name_to_xattr(bool posix_extensions,
> + const char *ea_name, size_t ea_name_len,
> + char *attr_name)
> +{
> + if (posix_extensions &&
> + ksmbd_is_posix_ea_name(ea_name, ea_name_len)) {
why the check for allowed namespaces via ksmbd_is_posix_ea_name() at all
and not just pass through whatever the client sends us, pass it down and
let the xattr subsystem deal with it?
Still wrapping my head around this so I might be missing something
obvious. :)
Thanks!
-slow
OpenPGP_signature.asc
(application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEE+uLGCIokJSBRxVnkqh6bcSY5nkYFAmpdxuYFAwAAAAAACgkQqh6bcSY5nkbj iQ//f5PwnqJKZ98At3MGhqMb/NCSXnnEk785RIKWfsiZW/YmGYcqe7VvMd9NtYSwam/rY/sDqhF+ tIwwyXbMGNg93jnzc2T+7mjcHx8wDQnnhST4pyD+zcgvveADaQUzbY5HSj3kVgq2FZ8ZNqA/3lS3 34Z6cFFCi6fIjHv88gxwRPq40EhnRu6kuJBvIYXARfX7IBwHjh7TlSIdkRGiMXXhOh9JSriDkdHa /8oVDmozfJB6jX0WqI4y4FmFXJN6QZUmw/wrRCrarlKazV6/NYDlTiMHidgL4ZKu8sxECjgNrHod p/vHzM/cd8SzV+nMZWd0BuAkK/gAkKImHmnYipvQR+ks/Tx5AuuL+TgFOl8ihFOENW427Ee4VnIG EoBUqAc6n/8pfWkQEfT3ovTu6KElH3UnioCp49WM/hEM+lhcmaWclldx+70YCm/ZxLlxaCU1Jmoa tFPM+yMTvPKbkMz3ZyiDjppSwMfDoY7ya9TFFDjDzz75dJdQrP96ek45P9zKZNJXcVYMb+IImeUA P4Q6rCgX6GCdltDWsKQZbpuijtHT9IwrFgSxyPTXpVYNWmYMKLhCi75lEVH/OYxSqc9QouihdQym KGW7d3E/wTfdnZ+7RgcppdbafE8PEaZpkpU+p3yDu12EZEcueuUGBMoQpMFqdHbwC01JGYd86q+M kXw= =wCTD -----END PGP SIGNATURE-----