From: Chuck Lever <cel@kernel.org>
To: Donald Hunter <donald.hunter@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>, Shuah Khan <shuah@kernel.org>,
Jeff Layton <jlayton@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] nfsd: add NFSD_CMD_FILEHANDLE_GET for root filehandle lookup
Date: Wed, 21 Oct 2026 15:20:06 -0400 [thread overview]
Message-ID: <179261039943.1716542.9468280490238427804.b4-ty@b4> (raw)
In-Reply-To: <20261021-nfsd-filehandle-get-v2-1-bd7fc8b1b783@kernel.org>
On Wed, 21 Oct 2026 07:44:13 -0400, Jeff Layton wrote:
> rpc.mountd still fetches export root filehandles via the
> /proc/fs/nfsd/filehandle transaction interface to satisfy v2/3 MNT
> requests.
>
> Add a netlink equivalent:
>
> FILEHANDLE_GET takes domain, path and maxsize and replies with the
> composed handle, like write_filehandle(). Unlike /proc, which silently
> clamps maxsize to NFS3_FHSIZE, maxsize outside [NFS_FHSIZE, NFS3_FHSIZE]
> is rejected with -ERANGE. Include a kselftest covering validation and
> byte-parity with the /proc interface.
>
> [...]
Applied to nfsd-testing, thanks!
[1/1] nfsd: add NFSD_CMD_FILEHANDLE_GET for root filehandle lookup
commit: c9d646d1dd8b2fd96548d3f22fc709a84dc6f3e0
--
Chuck Lever
prev parent reply other threads:[~2026-10-21 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 11:44 [PATCH v2] nfsd: add NFSD_CMD_FILEHANDLE_GET for root filehandle lookup Jeff Layton
2026-10-21 19:20 ` Chuck Lever [this message]
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=179261039943.1716542.9468280490238427804.b4-ty@b4 \
--to=cel@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jlayton@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=netdev@vger.kernel.org \
--cc=okorniev@redhat.com \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=tom@talpey.com \
--cc=trondmy@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