From: Ralph Boehme <slow@samba.org>
To: Ze Tan <tanze@kylinos.cn>,
sfrench@samba.org, linkinjeon@kernel.org, pc@manguebit.org,
sprasad@microsoft.com, tom@talpey.comm, senozhatsky@chromium.org,
chenxiaosong@chenxiaosong.com, linux-cifs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 6/9] ksmbd: support security.capability EAs
Date: Mon, 20 Jul 2026 08:57:42 +0200 [thread overview]
Message-ID: <48439a79-aa0c-4f0d-b079-3b85de715226@samba.org> (raw)
In-Reply-To: <846fec356d359126e64ea64cd5f6e80ce7de4b61.1784258165.git.tanze@kylinos.cn>
[-- Attachment #1.1: Type: text/plain, Size: 768 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2026-07-20 6:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 3:39 [RFC PATCH v2 0/9] smb: support security and trusted xattrs over EAs Ze Tan
2026-07-17 3:39 ` [RFC PATCH v2 1/9] smb: client: support security.capability " Ze Tan
2026-07-20 5:21 ` Namjae Jeon
2026-07-17 3:39 ` [RFC PATCH v2 2/9] smb: client: support security.xfstests " Ze Tan
2026-07-17 3:39 ` [RFC PATCH v2 3/9] smb: client: support trusted xattrs " Ze Tan
2026-07-17 3:39 ` [RFC PATCH v2 4/9] ksmbd: extract SMB EA backing xattr name mapping Ze Tan
2026-07-17 3:39 ` [RFC PATCH v2 5/9] ksmbd: extract SMB EA response name handling Ze Tan
2026-07-17 3:39 ` [RFC PATCH v2 6/9] ksmbd: support security.capability EAs Ze Tan
2026-07-20 6:57 ` Ralph Boehme [this message]
2026-07-20 13:06 ` tanze
2026-07-21 13:38 ` Ralph Boehme
2026-07-21 16:41 ` Steve French
2026-07-21 17:10 ` Ralph Boehme
2026-07-17 3:39 ` [RFC PATCH v2 7/9] ksmbd: support security.xfstests EAs Ze Tan
2026-07-20 5:03 ` Namjae Jeon
2026-07-20 6:33 ` tanze
2026-07-20 6:36 ` tanze
2026-07-17 3:39 ` [RFC PATCH v2 8/9] ksmbd: support trusted EAs Ze Tan
2026-07-17 3:39 ` [RFC PATCH v2 9/9] ksmbd: avoid self oplock breaks for EA opens Ze Tan
2026-07-20 5:34 ` Namjae Jeon
2026-07-20 8:54 ` tanze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48439a79-aa0c-4f0d-b079-3b85de715226@samba.org \
--to=slow@samba.org \
--cc=chenxiaosong@chenxiaosong.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=senozhatsky@chromium.org \
--cc=sfrench@samba.org \
--cc=sprasad@microsoft.com \
--cc=tanze@kylinos.cn \
--cc=tom@talpey.comm \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®