diff options
| author | Christian Brauner <brauner@kernel.org> | 2025-06-06 11:45:09 +0200 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2025-06-11 11:59:08 +0200 |
| commit | 7f4f229195b73606ded77e56943f463b78adf635 (patch) | |
| tree | 552a87c24c71f2fbaa69871a470889dda0ca9896 /fs/namespace.c | |
| parent | 9b0240b3ccc325c7a96cf362877180bc9e10d546 (diff) | |
| download | tip-7f4f229195b73606ded77e56943f463b78adf635.tar.gz | |
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 'fs/namespace.c')
| -rw-r--r-- | fs/namespace.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/fs/namespace.c b/fs/namespace.c index e13d9ab4f56496..7ca4612c7ae929 100644 --- a/fs/namespace.c +++ b/fs/namespace.c @@ -6203,9 +6203,11 @@ static void __init init_mount_tree(void) if (IS_ERR(mnt)) panic("Can't create rootfs"); - ns = alloc_mnt_ns(&init_user_ns, false); + ns = alloc_mnt_ns(&init_user_ns, true); if (IS_ERR(ns)) panic("Can't allocate initial namespace"); + ns->seq = atomic64_inc_return(&mnt_ns_seq); + ns->ns.inum = PROC_MNT_INIT_INO; m = real_mount(mnt); ns->root = m; ns->nr_mounts = 1; |