From: Neill Kapron <nkapron@google.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Stephen Smalley <stephen.smalley.work@gmail.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, 5 Sep 2025 22:48:08 +0000 [thread overview]
Message-ID: <aLtoqKL8plKOF0Ed@google.com> (raw)
In-Reply-To: <e2c4c055ff356b4fe5d49bc9df3fd2ab@paul-moore.com>
On Thu, Sep 04, 2025 at 04:15:52PM -0400, Paul Moore wrote:
>
> Merged into selinux/dev, thanks!
>
My appologies, I introduced a logic bug between v1 and v2, and have sent
a patch which fixes it [1].
Thanks,
Neill
[1] https://lore.kernel.org/selinux/20250905222656.3692837-1-nkapron@google.com/
prev parent reply other threads:[~2025-09-05 22:48 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
2025-09-04 20:15 ` Paul Moore
2025-09-05 22:48 ` Neill Kapron [this message]
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=aLtoqKL8plKOF0Ed@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).