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] selinux: fix logic issue with per-file labeling for functionfs
Date: Sat, 6 Sep 2025 03:15:19 +0000 [thread overview]
Message-ID: <aLunR_0BPCrATnBP@google.com> (raw)
In-Reply-To: <CAHC9VhT8NrsXMM-PPZJ0EPLxFHQ1vOu+ASCd+82Xth_mJPnDiA@mail.gmail.com>
On Fri, Sep 05, 2025 at 10:13:01PM -0400, Paul Moore wrote:
>
> With the original patch sitting at the top of the selinux/dev branch,
> are you okay if I simply fixup the existing patch by adding the
> missing '!'?
>
Yes, that is fine by me. I could submit a v4 if you would prefer that.
Sorry for the thrash,
Neill
next prev parent reply other threads:[~2025-09-06 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 22:26 [PATCH] selinux: fix logic issue with per-file labeling for functionfs Neill Kapron
2025-09-06 2:13 ` Paul Moore
2025-09-06 3:15 ` Neill Kapron [this message]
2025-09-07 16:58 ` Paul Moore
2025-09-07 18:46 ` 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=aLunR_0BPCrATnBP@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.