From: Christian Brauner <brauner@kernel.org>
To: Aleksa Sarai <cyphar@cyphar.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
Jonathan Corbet <corbet@lwn.net>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH RFC v2 0/4] procfs: make reference pidns more user-visible
Date: Thu, 24 Jul 2025 09:36:52 +0200 [thread overview]
Message-ID: <20250724-bekunden-einplanen-160f57e944e9@brauner> (raw)
In-Reply-To: <20250723-procfs-pidns-api-v2-0-621e7edd8e40@cyphar.com>
On Wed, Jul 23, 2025 at 09:18:50AM +1000, Aleksa Sarai wrote:
> Ever since the introduction of pid namespaces, procfs has had very
> implicit behaviour surrounding them (the pidns used by a procfs mount is
> auto-selected based on the mounting process's active pidns, and the
> pidns itself is basically hidden once the mount has been constructed).
>
> /* pidns mount option for procfs */
I like it. I think this will be very useful!
Fwiw, I think sysfs could probably use the same treatment.
It should probably gain a pidns & netns mount option and the ioctls to
get those out of sysfs so you know where that sysfs belongs. Thoughts?
prev parent reply other threads:[~2025-07-24 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 23:18 [PATCH RFC v2 0/4] procfs: make reference pidns more user-visible Aleksa Sarai
2025-07-22 23:18 ` [PATCH RFC v2 1/4] pidns: move is-ancestor logic to helper Aleksa Sarai
2025-07-24 7:06 ` Christian Brauner
2025-07-22 23:18 ` [PATCH RFC v2 2/4] procfs: add "pidns" mount option Aleksa Sarai
2025-07-24 7:25 ` Christian Brauner
2025-07-25 2:13 ` Aleksa Sarai
2025-07-22 23:18 ` [PATCH RFC v2 3/4] procfs: add PROCFS_GET_PID_NAMESPACE ioctl Aleksa Sarai
2025-07-24 7:34 ` Christian Brauner
2025-07-25 2:24 ` Aleksa Sarai
2025-07-31 10:31 ` Christian Brauner
2025-07-31 14:21 ` Aleksa Sarai
2025-07-22 23:18 ` [PATCH RFC v2 4/4] selftests/proc: add tests for new pidns APIs Aleksa Sarai
2025-07-24 7:36 ` Christian Brauner [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=20250724-bekunden-einplanen-160f57e944e9@brauner \
--to=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=cyphar@cyphar.com \
--cc=jack@suse.cz \
--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=shuah@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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