[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <173643164044.18486.14928337621532013382.b4-ty@oracle.com>
Date: Thu, 9 Jan 2025 09:10:06 -0500
From: cel@...nel.org
To: Donald Hunter <donald.hunter@...il.com>,
Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>,
Neil Brown <neilb@...e.de>,
Olga Kornievskaia <okorniev@...hat.com>,
Dai Ngo <Dai.Ngo@...cle.com>,
Tom Talpey <tom@...pey.com>,
Trond Myklebust <trondmy@...nel.org>,
Anna Schumaker <anna@...nel.org>,
Jeff Layton <jlayton@...nel.org>
Cc: Chuck Lever <chuck.lever@...cle.com>,
Scott Mayhew <smayhew@...hat.com>,
Yongcheng Yang <yoyang@...hat.com>,
netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-nfs@...r.kernel.org
Subject: Re: [PATCH] lockd: add netlink control interface
From: Chuck Lever <chuck.lever@...cle.com>
On Wed, 08 Jan 2025 16:00:15 -0500, Jeff Layton wrote:
> The legacy rpc.nfsd tool will set the nlm_grace_period if the NFSv4
> grace period is set. nfsdctl is missing this functionality, so add a new
> netlink control interface for lockd that it can use. For now, it only
> allows setting the grace period, and the tcp and udp listener ports.
>
> lockd currently uses module parameters and sysctls for configuration, so
> all of its settings are global. With this change, lockd now tracks these
> values on a per-net-ns basis. It will only fall back to using the global
> values if any of them are 0.
>
> [...]
Applied to nfsd-testing, thanks!
This seems utterly reasonable to me. I'm thinking that it's a bit
late for v6.14, so for the moment it is parked in the testing
branch.
[1/1] lockd: add netlink control interface
commit: c7ec1d59e4adf1660eec9e5ec0ee83f4a32c0a49
--
Chuck Lever
Powered by blists - more mailing lists