From: Neill Kapron <nkapron@google.com>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: Paul Moore <paul@paul-moore.com>,
Ondrej Mosnacek <omosnace@redhat.com>,
kernel-team@android.com, selinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] selinux: enable per-file labeling for functionfs
Date: Fri, 29 Aug 2025 16:31:21 +0000 [thread overview]
Message-ID: <aLHV2Tb5aw1Znfw8@google.com> (raw)
In-Reply-To: <CAEjxPJ7-M5OAiTLmOynP36HF6XmJKhH2kTFAGmhg8ohCkZuT8w@mail.gmail.com>
On Fri, Aug 29, 2025 at 08:18:08AM -0400, Stephen Smalley wrote:
> As before, don't rely on the policy capability bit remaining stable
> until Paul merges this patch.
> Also, not worth re-spinning IMHO but the changelog below normally goes
> after the "---" before
> the diffstat so that it doesn't get included in the commit message
> since no one cares about
> the in-submission changes once the patch is merged.
Thanks, I appreciate your guidance on this!
Neill
next prev parent reply other threads:[~2025-08-29 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 17:03 [PATCH v3] selinux: enable per-file labeling for functionfs Neill Kapron
2025-08-29 12:18 ` Stephen Smalley
2025-08-29 16:31 ` Neill Kapron [this message]
2025-09-04 20:15 ` Paul Moore
2025-09-05 22:48 ` Neill Kapron
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=aLHV2Tb5aw1Znfw8@google.com \
--to=nkapron@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.