summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2025-06-06 11:45:08 +0200
committerChristian Brauner <brauner@kernel.org>2025-06-11 11:59:08 +0200
commit9b0240b3ccc325c7a96cf362877180bc9e10d546 (patch)
treeeacee4a3fe6794b52a141a1a5f6976f03bea38c7 /include/linux
parent6a9e2fb1bab53b54d02714a2ee3c6612d19629ce (diff)
downloadlinux-9b0240b3ccc325c7a96cf362877180bc9e10d546.tar.gz
linux-9b0240b3ccc325c7a96cf362877180bc9e10d546.zip
netns: 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 network 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-2-b8749c9a8844@kernel.org Reviewed-by: Jakub Kicinski <kuba@kernel.org> Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'include/linux')
-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 e77a37b23ca7..3ff0bd381704 100644
--- a/include/linux/proc_ns.h
+++ b/include/linux/proc_ns.h
@@ -47,6 +47,7 @@ enum {
PROC_PID_INIT_INO = PID_NS_INIT_INO,
PROC_CGROUP_INIT_INO = CGROUP_NS_INIT_INO,
PROC_TIME_INIT_INO = TIME_NS_INIT_INO,
+ PROC_NET_INIT_INO = NET_NS_INIT_INO,
};
#ifdef CONFIG_PROC_FS