[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <172925869887.229855.13686777853029850318.b4-ty@oracle.com>
Date: Fri, 18 Oct 2024 09:38:54 -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] lockd: Fix comment about NLMv3 backwards compatibility
From: Chuck Lever <chuck.lever@...cle.com>
On Fri, 13 Sep 2024 00:53:20 +0200, Pali Rohár wrote:
> NLMv2 is completely different protocol than NLMv1 and NLMv3, and in
> original Sun implementation is used for RPC loopback callbacks from statd
> to lockd services. Linux does not use nor does not implement NLMv2.
>
> Hence, NLMv3 is not backward compatible with NLMv2. But NLMv3 is backward
> compatible with NLMv1. Fix comment.
>
> [...]
Applied to nfsd-next for v6.13, thanks!
[1/1] lockd: Fix comment about NLMv3 backwards compatibility
commit: 6c64686e6bb8b5ec1e3cca4f495ba38341666745
--
Chuck Lever
Powered by blists - more mailing lists