Re: [RFC PATCH v2 1/9] smb: client: support security.capability over EAs

On Fri, Jul 17, 2026 at 12:40 PM Ze Tan <[email protected]> wrote:
>
> generic/093 uses setcap and getcap to check that a write clears the file
> capability. The CIFS client does not have a security xattr handler, so
> these commands cannot set or read security.capability through SMB EAs.
>
> Register a security xattr handler and build the complete EA name for
> SET_INFO and QUERY_INFO. Keep security.capability unchanged in EA lists.
> Reject other security xattrs.
>
> Signed-off-by: Ze Tan <[email protected]>
The client exposes these EA names through security.* regardless of
whether SMB3 POSIX extensions were
negotiated. Is that right?