From: Paul Moore <paul@paul-moore.com>
To: "Christian Göttsche" <cgoettsche@seltendoof.de>
Cc: "Christian Göttsche" <cgzones@googlemail.com>,
"Stephen Smalley" <stephen.smalley.work@gmail.com>,
"Ondrej Mosnacek" <omosnace@redhat.com>,
"Casey Schaufler" <casey@schaufler-ca.com>,
"John Johansen" <john.johansen@canonical.com>,
"Thiébaud Weksteen" <tweek@google.com>,
"Bram Bonné" <brambonne@google.com>,
"Canfeng Guo" <guocanfeng@uniontech.com>,
"GUO Zihua" <guozihua@huawei.com>,
selinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 2/6] selinux: contify network namespace pointer
Date: Fri, 11 Apr 2025 16:29:34 -0400 [thread overview]
Message-ID: <ec975217c9bc8155f454a1dc7b3341ea@paul-moore.com> (raw)
In-Reply-To: <20250318083422.21489-1-cgoettsche@seltendoof.de>
On Mar 18, 2025 =?UTF-8?q?Christian=20G=C3=B6ttsche?= <cgoettsche@seltendoof.de> wrote:
>
> The network namespace is not modified.
>
> Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
> ---
> security/selinux/include/objsec.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Merged into selinux/dev, thanks.
--
paul-moore.com
prev parent reply other threads:[~2025-04-11 20:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 8:33 [RFC PATCH 2/6] selinux: contify network namespace pointer Christian Göttsche
2025-03-18 8:33 ` [RFC PATCH 3/6] selinux: add likely hints for fast paths Christian Göttsche
2025-04-11 20:29 ` [PATCH RFC " Paul Moore
2025-03-18 8:33 ` [RFC PATCH 4/6] selinux: improve network lookup failure warnings Christian Göttsche
2025-04-11 20:29 ` [PATCH RFC " Paul Moore
2025-04-15 14:28 ` Christian Göttsche
2025-05-20 21:09 ` Paul Moore
2025-03-18 8:33 ` [RFC PATCH 5/6] selinux: unify OOM handling in network hashtables Christian Göttsche
2025-04-11 20:29 ` [PATCH RFC " Paul Moore
2025-03-18 8:33 ` [RFC PATCH 6/6] selinux: add cache stats for network tables Christian Göttsche
2025-03-18 8:33 ` [RFC PATCH 1/6] selinux: constify network address pointer Christian Göttsche
2025-04-11 20:29 ` [PATCH RFC " Paul Moore
2025-04-11 20:29 ` Paul Moore [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=ec975217c9bc8155f454a1dc7b3341ea@paul-moore.com \
--to=paul@paul-moore.com \
--cc=brambonne@google.com \
--cc=casey@schaufler-ca.com \
--cc=cgoettsche@seltendoof.de \
--cc=cgzones@googlemail.com \
--cc=guocanfeng@uniontech.com \
--cc=guozihua@huawei.com \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=tweek@google.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.