From: NeilBrown <neilb@suse.com>
To: "Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fcntl.2, read.2, write.2: document "Lost locks" as cause for EIO.
Date: Wed, 20 Dec 2017 07:30:06 +1100 [thread overview]
Message-ID: <87h8smlaup.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <130530e8-83bc-35d3-b84c-9bee85ddee12@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2202 bytes --]
On Tue, Dec 19 2017, Michael Kerrisk (man-pages) wrote:
> On 12/18/2017 10:45 PM, NeilBrown wrote:
>> On Mon, Dec 18 2017, Michael Kerrisk (man-pages) wrote:
>>
>>> Hello Neil
>>>
>>> There's a piece of your patch I don't understand. Please see below.
>>>
>>> On 12/13/2017 05:19 AM, NeilBrown wrote:
>>>>
>>>> If an advisory lock is lost, then read/write requests on any
>>>> affected file descriptor can return EIO - for NFSv4 at least.
>>>>
>>>> Signed-off-by: NeilBrown <neilb@suse.com>
>>>> ---
>>>> man2/fcntl.2 | 24 ++++++++++++++++++++++++
>>>> man2/read.2 | 9 +++++++++
>>>> man2/write.2 | 9 +++++++++
>>>> 3 files changed, 42 insertions(+)
>>>>
>>>> diff --git a/man2/fcntl.2 b/man2/fcntl.2
>>>> index 67642384154c..6e6e26f66aa0 100644
>>>> --- a/man2/fcntl.2
>>>> +++ b/man2/fcntl.2
>>>> @@ -669,6 +669,30 @@ and
>>>> Mandatory locking is not specified by POSIX.
>>>> Some other systems also support mandatory locking,
>>>> although the details of how to enable it vary across systems.
>>>> +.SS Lost locks
>>>> +When an advisory lock is obtained on a networked filesystem such as
>>>> +NFS it is possible that the lock might get lost.
>>>> +This may happen due to administrative action on the server, or due to a
>>>> +network partition which lasts long enough for the server to assume
>>>
>>> What does "network partition which lasts long enough" mean?
>>> I think this perhaps needs to be clarified a little. At least,
>>> I don't understand it.
>>
>> "network partition" is a term using the NFS RFCs for any situation that
>> that results in the server and client not being able to communicate
>> (that are partitioned, one from the other? There is partition (wall)
>> between them? They are in separate partitions?).
>> I can see how the meaning might not be obvious if you hadn't come across
>> it before.
>>
>> If we change "network partition" to "loss of connectivity", would that
>> make it clear. Is "loss of network connectivity with the server" too
>> verbose?
>
> Thanks, Neil. I've applied your patch and added the words "loss of network
> connectivity with the server".
Looks good. Thanks!
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-12-19 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 4:19 [PATCH] fcntl.2, read.2, write.2: document "Lost locks" as cause for EIO NeilBrown
2017-12-18 16:46 ` Michael Kerrisk (man-pages)
2017-12-18 21:45 ` NeilBrown
2017-12-19 5:48 ` Michael Kerrisk (man-pages)
2017-12-19 20:30 ` NeilBrown [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=87h8smlaup.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mtk.manpages@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;
as well as URLs for NNTP newsgroup(s).