Re: [PATCH 00/15] smb: add native security and trusted xattrs
Ralph Boehme <[email protected]> Sat, 25 Jul 2026 10:24:30 +0200
| Newsgroups | org.kernel.vger.linux-cifs |
|---|---|
| Message-ID | <[email protected]> |
Hi Ze, On 7/25/26 8:56 AM, tanze wrote: > For a handle opened with an SMB3 POSIX create context, the mapping in > this series is: > > Client-visible xattr Protocol EA name Server xattr > ----------------------------------------------------------------------- > user.foo foo user.foo > security.capability security.capability security.capability > security.xfstests security.xfstests security.xfstests > trusted.foo trusted.foo trusted.foo thanks! I'm personally strongly leaning towards having a protocol design that carries the namespace for *all* namespaces including user. Special casing the user namespace just for the sake of avoiding a clean design with a protocol version bump should be avoided. As said before, I'm happy to help and work on the protocol spec and documentation side of things. I suggest we wait for more feedback on the design from others, particularly Volker, metze, Jeremy and Tom. Thanks! -slow
OpenPGP_signature.asc
(application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEE+uLGCIokJSBRxVnkqh6bcSY5nkYFAmpkcr4FAwAAAAAACgkQqh6bcSY5nkb3 KQ//TVYgW9YBdczqDu465yBTfluISM46CAj2CY3bMmHt/hHszbaelt4HJMxttBXHn++TZq7dODgj X1hf8KN/qKnl4JfjRRvE59wpBQFUjU2sidophxg37Z8lWsz0VRVuN89xp0cuy3PVEqWbBmYV7Kui r6RTgeD3D3oJu8i2tMvC+87XWjD3wfuVgjnhSAlbIgZbYOScnvZSSa2Cv0loKpX1TU+eFKg3KJPT qoI3xIX5VcjkT8cHRj5q8dK/12yjhXtqM0s//7LaLN3s2p6qYdd2je1NMLbsAHbedH6khrTUAbRY lATsQZBEIUWaAeh5rkOYif3mZPfA+cDUigyBznE7uYDyVAmf+2JCBLrIZi4XxwqLE2KFuHOxUUZ/ 9VpWDWYM7cDoBBfquFeoOvC+dbPIB7plxrggrXizMfGQ0BzfpnUVjFCNrqoNGVTa1PVk7TIJkgUz BJwPMN53q6oYNGcMRrg+ZI6K3Br/7l/pHqaGBaVTjzpABFOxOE5axY2DY6T7NJKOl0R4EzA0vx55 RWfL4npTCjCOUIyE1KYb//I35RFRVCkM0TwnnpaQAzKYvi9HyVCOaWLpSO94wIf9mqaXjAvGi8CG 4zGO9mzaEw8C/zHpaf12bpX3h8xb+UXQOh/0pOOrq+QLZ8E1q09XICQfV6903pf617oIy5l6niAd M3U= =AAFO -----END PGP SIGNATURE-----