Re: [PATCH 00/15] smb: add native security and trusted xattrs
Steve French <[email protected]> Mon, 27 Jul 2026 19:35:37 -0500
| Newsgroups | org.kernel.vger.linux-cifs |
|---|---|
| Message-ID | <CAH2r5mu7Ra8vxkR4sNUy560FX5=R7pMzA-7k19p1j5bV28V-+w@mail.gmail.com> |
What other protocol improvements should go into the new version of the prot= ocol? On Sat, Jul 25, 2026 at 3:24=E2=80=AFAM Ralph Boehme <[email protected]> wrote= : > > 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.capabili= ty > > 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 --=20 Thanks, Steve