linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 0/3] nsfs: expose the stable inode numbers in a public header
@ 2025-06-06  9:45 Christian Brauner
  2025-06-06  9:45 ` [PATCH 1/3] nsfs: move root inode number to uapi Christian Brauner
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Christian Brauner @ 2025-06-06  9:45 UTC (permalink / raw)
  To: linux-fsdevel, netdev
  Cc: David S. Miller, Eric Dumazet, Jakub Kicinski, Christian Brauner

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2025-06-09 22:46 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-06  9:45 [PATCH 0/3] nsfs: expose the stable inode numbers in a public header Christian Brauner
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

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).