summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2026-05-12 21:13:52 +0300
committerChuck Lever <cel@kernel.org>2026-06-09 23:32:59 +0300
commit1b0490e6a0849f2f9e9bd901a8a151368f57030f (patch)
tree3a7fda4187d3e96f46eacc1bf039b88a40f0dbb8 /include/linux
parent954a3f3f6cff4144f9bfafb676089250f57b9b00 (diff)
downloadlinux-1b0490e6a0849f2f9e9bd901a8a151368f57030f.tar.xz
lockd: Use xdrgen XDR functions for the NLMv3 UNLOCK procedure
The NLM UNLOCK procedure allows clients to release held locks, completing the basic lock lifecycle alongside TEST, LOCK, and CANCEL procedures already converted in this series. Convert UNLOCK to use the xdrgen functions nlm_svc_decode_nlm_unlockargs and nlm_svc_encode_nlm_res generated from the NLM version 3 protocol specification, reusing the nlm3svc_lookup_host() and nlm3svc_lookup_file() helpers introduced earlier in the series. The procedure handler uses xdrgen types through a wrapper structure that bridges between generated code and the legacy lockd_lock representation still used by the core lockd logic. Setting pc_argzero to zero is safe because the generated decoder fills the argp->xdrgen subfields before the procedure runs, so the zeroing memset performed by the dispatch layer is not needed. The lock member of the wrapper is populated explicitly in nlm3svc_lookup_file() rather than relying on zero-initialization. Reviewed-by: Jeff Layton <jlayton@kernel.org> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions