[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZlRzNquWNalhYtux@infradead.org>
Date: Mon, 27 May 2024 04:49:10 -0700
From: "hch@...radead.org" <hch@...radead.org>
To: Trond Myklebust <trondmy@...merspace.com>
Cc: "cyphar@...har.com" <cyphar@...har.com>,
"hch@...radead.org" <hch@...radead.org>,
"jack@...e.cz" <jack@...e.cz>,
"brauner@...nel.org" <brauner@...nel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"chuck.lever@...cle.com" <chuck.lever@...cle.com>,
"alex.aring@...il.com" <alex.aring@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"jlayton@...nel.org" <jlayton@...nel.org>,
"amir73il@...il.com" <amir73il@...il.com>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>
Subject: Re: [PATCH RFC v2] fhandle: expose u64 mount id to
name_to_handle_at(2)
On Sun, May 26, 2024 at 10:32:39PM +0000, Trond Myklebust wrote:
> I assume the reason is to give the caller a race free way to figure out
> which submount the path resolves to.
But the handle op are global to the file systems (aka super_block). It
does not matter what mount you use to access it.
Snip random things about userland NFS servers I couldn't care less
about..
Powered by blists - more mailing lists