From: Jakub Kicinski <kuba@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH 2/3] netns: use stable inode number for initial mount ns
Date: Mon, 9 Jun 2025 15:46:37 -0700 [thread overview]
Message-ID: <20250609154637.06f27fde@kernel.org> (raw)
In-Reply-To: <20250606-work-nsfs-v1-2-b8749c9a8844@kernel.org>
On Fri, 06 Jun 2025 11:45:08 +0200 Christian Brauner wrote:
> 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.
Nice!
Reviewed-by: Jakub Kicinski <kuba@kernel.org>
next prev parent reply other threads:[~2025-06-09 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=20250609154637.06f27fde@kernel.org \
--to=kuba@kernel.org \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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).