From: "Mickaël Salaün" <mic@digikod.net>
To: Christian Brauner <brauner@kernel.org>
Cc: "Paul Moore" <paul@paul-moore.com>,
"Günther Noack" <gnoack@google.com>,
"Serge E . Hallyn" <serge@hallyn.com>,
"Daniel Durning" <danieldurning.work@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Justin Suess" <utilityemal77@gmail.com>,
"Lennart Poettering" <lennart@poettering.net>,
"Mikhail Ivanov" <ivanov.mikhail1@huawei-partners.com>,
"Nicolas Bouchinet" <nicolas.bouchinet@oss.cyber.gouv.fr>,
"Shervin Oloumi" <enlightened@google.com>,
"Tingmao Wang" <m@maowtm.org>,
kernel-team@cloudflare.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 1/9] security: add LSM blob and hooks for namespaces
Date: Fri, 24 Jul 2026 11:24:46 +0200 [thread overview]
Message-ID: <20260724.che1quaiPhee@digikod.net> (raw)
In-Reply-To: <20260710-sardinen-zinken-aerodynamik-8b09dafc60a2@brauner>
On Fri, Jul 10, 2026 at 08:55:21AM +0200, Christian Brauner wrote:
> On 2026-07-09 17:58 +0200, Mickaël Salaün wrote:
> > On Thu, Jul 09, 2026 at 09:03:58AM -0400, Paul Moore wrote:
> > > On Thu, Jul 9, 2026 at 5:12 AM Mickaël Salaün <mic@digikod.net> wrote:
> > > > On Wed, Jul 08, 2026 at 11:22:17PM -0400, Paul Moore wrote:
> > > > > On May 27, 2026 =?UTF-8?q?Micka=C3=ABl=20Sala=C3=BCn?= <mic@digikod.net> wrote:
> > > > > >
> > > > > > All namespace types now share the same ns_common infrastructure. Extend
> > > > > > this to include a security blob so LSMs can start managing namespaces
> > > > > > uniformly without having to add one-off hooks or security fields to
> > > > > > every individual namespace type.
> > >
> > > ...
> > >
> > > > > > @@ -91,7 +103,10 @@ int __ns_common_init(struct ns_common *ns, u32 ns_type, const struct proc_ns_ope
> > > > > >
> > > > > > void __ns_common_free(struct ns_common *ns)
> > > > > > {
> > > > > > - proc_free_inum(ns->inum);
> > > > > > + security_namespace_free(ns);
> > > > > > +
> > > > > > + if (ns->inum > MNT_NS_INO_SPECIAL_MAX)
> > > > > > + proc_free_inum(ns->inum);
> > > > >
> > > > > The ns->inum check in the if-conditional above isn't quite the same as
> > > > > the is_anon_ns() check it replaces in free_mnt_ns(). You touch on this
> > > > > a bit in the changelog, but that really should be explained in the
> > > > > commit description.
> > > > >
> > > > > ... or honestly, should that change be a separate patch?
> > > >
> > > > I think it's fine, but it's Christian's patch, so I'll let him answer
> > > > and propose a new commit description.
> > >
> > > I don't have a strong opinion on either approach, either a separate
> > > patch or doc update, but one of the two needs to happen.
> >
> > Noted, I'll follow on this with Christian.
>
> I think we should add this as a separate patch.
Ok, I wrote this patch and I'll sent it with v3.
next prev parent reply other threads:[~2026-07-24 9:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 18:11 [PATCH v2 0/9] Landlock: Namespace and capability control Mickaël Salaün
2026-05-27 18:11 ` [PATCH v2 1/9] security: add LSM blob and hooks for namespaces Mickaël Salaün
2026-06-05 15:06 ` Mickaël Salaün
2026-06-05 18:08 ` Paul Moore
2026-07-09 3:22 ` Paul Moore
2026-07-09 9:12 ` Mickaël Salaün
2026-07-09 13:03 ` Paul Moore
2026-07-09 15:58 ` Mickaël Salaün
2026-07-10 6:55 ` Christian Brauner
2026-07-24 9:24 ` Mickaël Salaün [this message]
2026-07-10 20:42 ` Paul Moore
2026-07-24 9:25 ` Mickaël Salaün
2026-05-27 18:11 ` [PATCH v2 2/9] security: Add LSM_AUDIT_DATA_NS for namespace audit records Mickaël Salaün
2026-05-27 18:11 ` [PATCH v2 3/9] landlock: Wrap per-layer access masks in struct layer_config Mickaël Salaün
2026-05-27 18:11 ` [PATCH v2 4/9] landlock: Enforce namespace use restrictions Mickaël Salaün
2026-05-27 18:11 ` [PATCH v2 5/9] landlock: Enforce capability restrictions Mickaël Salaün
2026-05-27 18:11 ` [PATCH v2 6/9] selftests/landlock: Add namespace restriction tests Mickaël Salaün
2026-05-27 18:11 ` [PATCH v2 7/9] selftests/landlock: Add capability " Mickaël Salaün
2026-05-27 18:11 ` [PATCH v2 8/9] samples/landlock: Add capability and namespace restriction support Mickaël Salaün
2026-05-27 18:11 ` [PATCH v2 9/9] landlock: Add documentation for capability and namespace restrictions Mickaël Salaün
2026-06-01 9:37 ` Günther Noack
2026-07-24 9:26 ` Mickaël Salaün
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=20260724.che1quaiPhee@digikod.net \
--to=mic@digikod.net \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=danieldurning.work@gmail.com \
--cc=enlightened@google.com \
--cc=gnoack@google.com \
--cc=ivanov.mikhail1@huawei-partners.com \
--cc=kernel-team@cloudflare.com \
--cc=lennart@poettering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=m@maowtm.org \
--cc=nicolas.bouchinet@oss.cyber.gouv.fr \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=utilityemal77@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