From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux Containers <containers@lists.linux.dev>
Subject: Re: [GIT PULL 05/17 for v6.19] namespaces
Date: Mon, 01 Dec 2025 13:06:02 -0600 [thread overview]
Message-ID: <87ecperpid.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <20251128-kernel-namespaces-v619-28629f3fc911@brauner> (Christian Brauner's message of "Fri, 28 Nov 2025 17:48:16 +0100")
Christian Brauner <brauner@kernel.org> writes:
> Hey Linus,
>
> /* Summary */
> This contains substantial namespace infrastructure changes including a new
> system call, active reference counting, and extensive header cleanups.
> The branch depends on the shared kbuild branch for -fms-extensions
> support.
I am missing something. From the description it looks like
you are making nested containers impossible once this feature
is adopted. Because the container will be able to see all of
the other namespaces and thus to see outside of it's own namespace.
The reason such as system call has not been introduced in the past
is because it introduces the namespace of namespace problem.
How have you solved the namespace of namespaces problem?
If you want nesting of containers the listing of namespaces very
much must be incomplete.
I haven't looked at reviewed or looked at the code yet because
the code was not posted in any of the usual places for container
development, nor was I copied.
Can you please describe how you are avoiding the namespace of namespaces
problem?
Eric
next parent reply other threads:[~2025-12-01 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251128-vfs-v619-77cd88166806@brauner>
[not found] ` <20251128-kernel-namespaces-v619-28629f3fc911@brauner>
2025-12-01 19:06 ` Eric W. Biederman [this message]
2025-12-02 17:00 ` [GIT PULL 05/17 for v6.19] namespaces Linus Torvalds
2025-12-03 10:07 ` Christian Brauner
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=87ecperpid.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=brauner@kernel.org \
--cc=containers@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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