Linux Security Modules development
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: josef@toxicpanda.com, linux-fsdevel@vger.kernel.org,
	linux-api@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-mm@kvack.org, linux-security-module@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ben Segall <bsegall@google.com>,
	Christian Brauner <brauner@kernel.org>,
	David Hildenbrand <david@kernel.org>,
	David Howells <dhowells@redhat.com>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ingo Molnar <mingo@redhat.com>, Jan Kara <jack@suse.cz>,
	Jonathan Corbet <corbet@lwn.net>,
	John Johansen <john.johansen@canonical.com>,
	Juri Lelli <juri.lelli@redhat.com>, Kees Cook <kees@kernel.org>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	"Liam R. Howlett" <liam@infradead.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	Manfred Spraul <manfred@colorfullife.com>,
	Mel Gorman <mgorman@suse.de>, Michal Hocko <mhocko@suse.com>,
	Mike Rapoport <rppt@kernel.org>, Neal Gompa <neal@gompa.dev>,
	Paul Moore <paul@paul-moore.com>,
	Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Serge Hallyn <sergeh@kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Valentin Schneider <vschneid@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
Subject: Re: [RFC PATCH v2 00/13] Namespace for namespace roots
Date: Wed, 18 Nov 2026 20:23:05 +0200	[thread overview]
Message-ID: <av3tCT5lQTu7qBMz@kernel.org> (raw)
In-Reply-To: <CALCETrXPLeUgxyhjP4XuWS46FKB0TUHF5PcMkdMf+qeEXbyXRA@mail.gmail.com>

On Wed, Nov 18, 2026 at 09:46:02AM -0800, Andy Lutomirski wrote:
> On Wed, Nov 18, 2026 at 9:08 AM Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > On Wed, Nov 18, 2026 at 07:04:21PM +0200, Jarkko Sakkinen wrote:
> > > On Wed, Nov 18, 2026 at 08:59:39AM -0800, Andy Lutomirski wrote:
> > > > On Tue, Nov 17, 2026 at 3:14 PM Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > > > >
> > > > > OVERVIEW
> > > > > ========
> > > > >
> > > > > A root namespace (rootns) is a kernel object backed by a file descriptor
> > > > > that binds together:
> > > > >
> > > > > 1. A full or partial set of detached namespaces.
> > > > > 2. A dedicated PID namespace for spawning processes into, signaling
> > > > >    members, and polling or waiting on PID 1 exit.
> > > > > 3. An initially empty mount namespace (CLONE_EMPTY_MNTNS) that must be
> > > > >    populated before going live, without inheriting host mount-tree
> > > > >    ancestors.
> > > > >
> > > > > Work on this feature started in 2025 from David Howells' container object
> > > > > patch set [1], which I turned into a namespace for namespace roots and
> > > > > rebuilt around that premise.
> > > > >
> > > > > While the patch set is manually written, the original motivation came
> > > > > from isolating LLM agents. Running untrusted agent workloads made it
> > > > > clear that OCI runtimes need to minimize their live configuration
> > > > > surface.
> > > > >
> > > > > Assembling mounts, credentials, and namespaces inside helper processes
> > > > > with a half-configured container is what I see as the main challenge,
> > > > > and the existential debate around namespaces and container objects is an
> > > > > unfocused discussion topic.
> > > >
> > > >
> > > > I've skimmed some of the series, and I see a bunch of good ideas that
> > > > involve using an fd to manage a thing.  But I'm wondering how much of
> > > > the value is added by that and how much is added by having a new
> > > > *type* of thing: the "rootns".
> > > >
> > > > How much of the value comes from the rootns vs the new APIs to
> > > > configure namespaces without entering them first?
> > > >
> > > > For that matter, the cells series also seems to contain a (possibly
> > > > very similar) variant of the same thing.
> > > >
> > > > Would it make sense to come up with a patchset that does *just* the
> > > > configure-a-namespace-by-fd part?  It seems to me that this should be
> > > > an easier thing to agree on, and it's a big part of the complexity of
> > > > all of this, and it solves a real problem even without
> > > > cells/rootnses/jails/whatever.
> > >
> > > Is it  more accurately scope the part that is "just the fd-part" and
> > > what you consider as "extra cruft"?
> 
> I'm not actually trying to say that anything is "extra cruft".  What I
> mean is: there seems to be somewhat of a core that is pretty similar
> between the two patchsets, and that core seems independently useful.
> 
> > >
> > > I.e., where do you draw the border?
> >
> > I'm asking this because I had similar thoughts when I started this back
> > in 2025. David had some good ideas but it did more than having a fd
> > that does not go live before everything is set up properly.
> 
> I don't know that I have a very clear border, but here's an example:
> 
> rootns has MOVE_MOUNT_T_ROOTNS_ROOT.
> 
> cells has:
> 
> +What else goes into the tree is mounted on it before it becomes a
> mount namespace.  A
> +filesystem for the cell to write to is mapped in the same way:
> +
> +.. code-block:: c
> +
> +   fs = fsopen("tmpfs", 0);
> +   fsconfig(fs, FSCONFIG_SET_STRING, "mode", "1777", 0);
> +   fsconfig(fs, FSCONFIG_CMD_CREATE, NULL, NULL, 0);
> +   mnt = fsmount(fs, 0, MOUNT_ATTR_NOSUID | MOUNT_ATTR_NODEV);
> +   mount_setattr(mnt, "", AT_EMPTY_PATH, &attr, sizeof(attr));
> +   move_mount(mnt, "", tree, "tmp", MOVE_MOUNT_F_EMPTY_PATH);
> 
> (Source: https://lore.kernel.org/all/20261105-b4-cells-v3-2-bc9095937a84@toxicpanda.com/)
> 
> I feel like you are both *so close* to something that would stand
> alone and make perfect sense.  I also feel like, if that's a goal,
> then both series are slightly off from the bulls-eye.  (Keep in mind
> that I've spend a total of about ten minutes looking at the relevant
> parts of the series.)

Thanks, there was still a lot of relevant feedback to address.

And who knows, perhaps there's a sweet spot intersection. I would not
mind that, as I only pursue for something simple and practical.

For the time being, I'll update this series simply because there's less
to change, and polish the implementation. That does not hurt even if
cells were the ultimate solution. Part of this series can still be
useful.

> 
> 
> -- 
> Andy Lutomirski
> AMA Capital Management, LLC

Br, Jarkko

      reply	other threads:[~2026-11-18 18:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 23:13 [RFC PATCH v2 00/13] Namespace for namespace roots Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 01/13] nsproxy: Pass nsproxy to create_new_namespaces() Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 02/13] rootns: Add core infrastructure for root namespaces Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 03/13] rootns: Track init lifecycle via copy_process() and pid_namespace Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 04/13] rootns: Add rootns_create() system call Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 05/13] rootns: Add rootns_wait() " Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 06/13] rootns: Add rootns_kill() " Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 07/13] fork: Support CLONE_INTO_ROOTNS in clone3() Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 08/13] fs: Support FSCONFIG_SET_ROOTNS in fsconfig() Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 09/13] fs: Support installing rootns mount trees via move_mount() Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 10/13] arch: Wire up rootns system calls Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 11/13] docs: Document root namespace uAPI Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 12/13] selftests/rootns: Add root namespace test suite Jarkko Sakkinen
2026-11-17 23:13 ` [RFC PATCH v2 13/13] MAINTAINERS: Add entry for ROOT NAMESPACE Jarkko Sakkinen
2026-11-18 14:47 ` [RFC PATCH v2 00/13] Namespace for namespace roots Josef Bacik
2026-11-18 15:28   ` Jarkko Sakkinen
2026-11-18 15:39     ` Jarkko Sakkinen
2026-11-18 15:46       ` Jarkko Sakkinen
2026-11-18 16:59 ` Andy Lutomirski
2026-11-18 17:04   ` Jarkko Sakkinen
2026-11-18 17:08     ` Jarkko Sakkinen
2026-11-18 17:30       ` Jarkko Sakkinen
2026-11-18 17:46       ` Andy Lutomirski
2026-11-18 18:23         ` Jarkko Sakkinen [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=av3tCT5lQTu7qBMz@kernel.org \
    --to=jarkko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=bsegall@google.com \
    --cc=corbet@lwn.net \
    --cc=dave@stgolabs.net \
    --cc=david@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jack@suse.cz \
    --cc=john.johansen@canonical.com \
    --cc=josef@toxicpanda.com \
    --cc=juri.lelli@redhat.com \
    --cc=kees@kernel.org \
    --cc=kprateek.nayak@amd.com \
    --cc=liam@infradead.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=luto@amacapital.net \
    --cc=manfred@colorfullife.com \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.com \
    --cc=mingo@redhat.com \
    --cc=neal@gompa.dev \
    --cc=paul@paul-moore.com \
    --cc=peterz@infradead.org \
    --cc=ptikhomirov@virtuozzo.com \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=rppt@kernel.org \
    --cc=sergeh@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=vschneid@redhat.com \
    --cc=zygmunt.krynicki@canonical.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