From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Christian Brauner <brauner@kernel.org>
Subject: [PATCH 0/3] nsfs: expose the stable inode numbers in a public header
Date: Fri, 06 Jun 2025 11:45:06 +0200 [thread overview]
Message-ID: <20250606-work-nsfs-v1-0-b8749c9a8844@kernel.org> (raw)
Userspace heavily relies on the root inode numbers for namespaces to
identify the initial namespaces. That's already a hard dependency. So we
cannot change that anymore. Move the initial inode numbers to a public
header and align the only two namespaces that currently don't do that
with all the other namespaces.
Signed-off-by: Christian Brauner <brauner@kernel.org>
---
Christian Brauner (3):
nsfs: move root inode number to uapi
netns: use stable inode number for initial mount ns
mntns: use stable inode number for initial mount ns
fs/namespace.c | 4 +++-
include/linux/proc_ns.h | 15 +++++++++------
include/uapi/linux/nsfs.h | 11 +++++++++++
net/core/net_namespace.c | 8 ++++++++
4 files changed, 31 insertions(+), 7 deletions(-)
---
base-commit: ec7714e4947909190ffb3041a03311a975350fe0
change-id: 20250606-work-nsfs-3e951f888309
next reply other threads:[~2025-06-06 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 9:45 Christian Brauner [this message]
2025-06-06 9:45 ` [PATCH 1/3] nsfs: move root inode number to uapi Christian Brauner
2025-06-06 9:45 ` [PATCH 2/3] netns: use stable inode number for initial mount ns Christian Brauner
2025-06-09 22:46 ` Jakub Kicinski
2025-06-06 9:45 ` [PATCH 3/3] mntns: " 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=20250606-work-nsfs-v1-0-b8749c9a8844@kernel.org \
--to=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).