[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <172849928288.133472.1345724004484528154.b4-ty@oracle.com>
Date: Wed, 9 Oct 2024 14:41:58 -0400
From: cel@...nel.org
To: Jeff Layton <jlayton@...nel.org>,
Neil Brown <neilb@...e.de>,
Olga Kornievskaia <okorniev@...hat.com>,
Dai Ngo <Dai.Ngo@...cle.com>,
Tom Talpey <tom@...pey.com>,
Pali Rohár <pali@...nel.org>
Cc: Chuck Lever <chuck.lever@...cle.com>,
linux-nfs@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] nfsd: Fill NFSv4.1 server implementation fields in OP_EXCHANGE_ID response
From: Chuck Lever <chuck.lever@...cle.com>
On Sat, 05 Oct 2024 20:33:49 +0200, Pali Rohár wrote:
> NFSv4.1 OP_EXCHANGE_ID response from server may contain server
> implementation details (domain, name and build time) in optional
> nfs_impl_id4 field. Currently nfsd does not fill this field.
>
> Send these information in NFSv4.1 OP_EXCHANGE_ID response. Fill them with
> the same values as what is Linux NFSv4.1 client doing. Domain is hardcoded
> to "kernel.org", name is composed in the same way as "uname -srvm" output
> and build time is hardcoded to zeros.
>
> [...]
Applied to nfsd-next for v6.13, thanks!
[1/1] nfsd: Fill NFSv4.1 server implementation fields in OP_EXCHANGE_ID response
commit: 5d063672154b3d2d3f9bc3426e0ee4e42ab0e811
--
Chuck Lever
Powered by blists - more mailing lists