From: bfields@fieldses.org (J. Bruce Fields)
To: Olga Kornievskaia <aglo@umich.edu>
Cc: Trond Myklebust <trondmy@gmail.com>,
linux-nfs <linux-nfs@vger.kernel.org>,
"nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [nfsv4] questing about NLM LOCK, CANCEL UNLOCK
Date: Thu, 7 Dec 2017 11:58:38 -0500 [thread overview]
Message-ID: <20171207165838.GA4096@fieldses.org> (raw)
In-Reply-To: <CAN-5tyEmwgo7ea1WJ-0nRE+Jz+b9rb97GkYEmFyq_C+8nr1kTw@mail.gmail.com>
On Thu, Dec 07, 2017 at 11:10:16AM -0500, Olga Kornievskaia wrote:
> Ok. I thought that because RFC1813 covers NLM operations that it is.
Yeah, I don't see a harm to the occasional NLM question on the v4
working group list. It's a bit of an orphaned protocol, so there's not
really any other implementation-independent forum.
> I will extend this question to the Linux NFS mailing list as the
> client implementation I'm interested is Linux.
But that's fine too.
I thought that LOCK/CANCEL race was one of the motivations for NFSv4,
so...
> >> Is there a solution or this is broken protocol?
... I'd always assumed the protocol was impossible to implement 100%
correctly, though maybe there's some clever solution.
> >> Should it be client's responsibility to notice that it received a LOCK
> >> reply for which it wasn't waiting and always follow up with an UNLOCK?
That would be tricky and still not handle all cases, I think.
--b.
next prev parent reply other threads:[~2017-12-07 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN-5tyEe2gEgmSnZju7MjgrFR_YK1PrLx2NpxJn5Ks88PEz__g@mail.gmail.com>
[not found] ` <CAABAsM57k0E32ywgW=qdhFbeHctcUivM9mkuuA1qbfB9F7Rvyg@mail.gmail.com>
2017-12-07 16:10 ` [nfsv4] questing about NLM LOCK, CANCEL UNLOCK Olga Kornievskaia
2017-12-07 16:58 ` J. Bruce Fields [this message]
2017-12-07 18:00 ` Olga Kornievskaia
2017-12-07 18:56 ` Frank Filz
2017-12-07 19:17 ` Olga Kornievskaia
2017-12-07 19:59 ` Frank Filz
2017-12-13 18:39 ` Olga Kornievskaia
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=20171207165838.GA4096@fieldses.org \
--to=bfields@fieldses.org \
--cc=aglo@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@ietf.org \
--cc=trondmy@gmail.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