From: "Chuck Lever" <cel@kernel.org>
To: "Olga Kornievskaia" <okorniev@redhat.com>,
"Chuck Lever" <chuck.lever@oracle.com>,
"Jeff Layton" <jlayton@kernel.org>
Cc: linux-nfs@vger.kernel.org, neilb@brown.name,
"Dai Ngo" <Dai.Ngo@oracle.com>, "Tom Talpey" <tom@talpey.com>
Subject: Re: [PATCH 1/1] lockd: fix GRANTED_MSG handling
Date: Fri, 26 Jun 2026 09:27:23 -0400 [thread overview]
Message-ID: <f911deb4-6476-4c8d-a22e-c61aedcab772@app.fastmail.com> (raw)
In-Reply-To: <20260625211852.31972-1-okorniev@redhat.com>
On Thu, Jun 25, 2026, at 5:18 PM, Olga Kornievskaia wrote:
> GRANTED_MSG is a server-to-client callback, so it runs on the client,
> where nfsd never registers nlmsvc_ops. The nlm4svc_lookup_host()/
> nlm3svc_lookup_host() helpers are for the server-side request handlers
> (TEST/LOCK/CANCEL/UNLOCK), which reach nlmsvc_ops->fopen and must
> reject requests when nfsd isn't running. GRANTED_MSG only calls
> nlmclnt_grant(). Instead, of calling nlm4svc_lookup_host()/
> nlm3svc_lookup_host() (which results in a client failing a GRANTED_MSG
> call) call nlmsvc_lookup_host.
>
> Fixes: 62721885e861 ("lockd: Use xdrgen XDR functions for the NLMv4
> GRANTED_MSG procedure")
> Fixes: 6c534ad999b6 ("lockd: Use xdrgen XDR functions for the NLMv3
> GRANTED_MSG procedure")
> Signed-off-by: Olga Kornievskaia <okorniev@redhat.com>
The fix LGTM.
Looking at this now, I see the patch targets two distinct
stable kernels. Therefore IMO this does actually need to be
two separate patches. I will split the patch when I apply
it to nfsd-testing.
--
Chuck Lever
prev parent reply other threads:[~2026-06-26 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 21:18 [PATCH 1/1] lockd: fix GRANTED_MSG handling Olga Kornievskaia
2026-06-26 1:49 ` NeilBrown
2026-06-26 13:27 ` 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=f911deb4-6476-4c8d-a22e-c61aedcab772@app.fastmail.com \
--to=cel@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
/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