summaryrefslogtreecommitdiff
path: root/include/linux/proc_ns.h
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2025-06-06 11:45:09 +0200
committerChristian Brauner <brauner@kernel.org>2025-06-11 11:59:08 +0200
commit7f4f229195b73606ded77e56943f463b78adf635 (patch)
tree552a87c24c71f2fbaa69871a470889dda0ca9896 /include/linux/proc_ns.h
parent9b0240b3ccc325c7a96cf362877180bc9e10d546 (diff)
downloadlwn-7f4f229195b73606ded77e56943f463b78adf635.tar.gz
lwn-7f4f229195b73606ded77e56943f463b78adf635.zip
mntns: use stable inode number for initial mount ns
Apart from the network and mount namespace all other namespaces expose a stable inode number and userspace has been relying on that for a very long time now. It's very much heavily used API. Align the mount namespace and use a stable inode number from the reserved procfs inode number space so this is consistent across all namespaces. Link: https://lore.kernel.org/20250606-work-nsfs-v1-3-b8749c9a8844@kernel.org Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'include/linux/proc_ns.h')
-rw-r--r--include/linux/proc_ns.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/proc_ns.h b/include/linux/proc_ns.h
index 3ff0bd381704..6258455e49a4 100644
--- a/include/linux/proc_ns.h
+++ b/include/linux/proc_ns.h
@@ -48,6 +48,7 @@ enum {
PROC_CGROUP_INIT_INO = CGROUP_NS_INIT_INO,
PROC_TIME_INIT_INO = TIME_NS_INIT_INO,
PROC_NET_INIT_INO = NET_NS_INIT_INO,
+ PROC_MNT_INIT_INO = MNT_NS_INIT_INO,
};
#ifdef CONFIG_PROC_FS