All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: smfrench@gmail.com, Tom Talpey <tom@talpey.com>,
	linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH v4] flock.2: add CIFS details
Date: Wed, 10 Mar 2021 20:07:02 +0100	[thread overview]
Message-ID: <45b64990-b879-02d3-28e5-b896af0502c4@gmail.com> (raw)
In-Reply-To: <20210304095026.782-1-aaptel@suse.com>



On 3/4/21 10:50 AM, Aurélien Aptel wrote:
> From: Aurelien Aptel <aaptel@suse.com>
> 
> Similarly to NFS, CIFS flock() locks behave differently than the
> standard. Document those differences.
> 
> Here is the rendered text:
> 
> CIFS details
>    In  Linux kernels up to 5.4, flock() is not propagated over SMB. A file
>    with such locks will not appear locked for remote clients.
> 
>    Since Linux 5.5, flock() locks are emulated with SMB  byte-range  locks
>    on  the  entire  file.  Similarly  to NFS, this means that fcntl(2) and
>    flock() locks interact with one another. Another important  side-effect
>    is  that  the  locks are not advisory anymore: a write on a locked file
>    will always fail with EACCES.   This difference originates from the de-
>    sign of locks in the SMB protocol, which provides mandatory locking se-
>    mantics. The nobrl mount option (see mount.cifs(8)) turns off  fnctl(2)
>    and  flock() lock propagation to remote clients and makes flock() locks
>    advisory again.
> 
> Signed-off-by: Aurelien Aptel <aaptel@suse.com>
> Reviewed-By: Tom Talpey <tom@talpey.com>
> ---
[...]
> +This difference originates from the design of locks in the SMB
> +protocol, which provides mandatory locking semantics. The
> +.I nobrl

I agree with Tom.  It's much easier to read if you just say that 'nobrl' 
torns off the non-locale behaviour, and acts as 5.4 and earlier kernels. 
  Unless there's any subtlety that makes it different.  Is there any?

BTW, you should use "semantic newlines":

$ man 7 man-pages |sed -n '/semantic newlines/,/^$/p'
    Use semantic newlines
        In the source of a manual page,  new  sentences  should  be
        started  on new lines, and long sentences should split into
        lines at clause breaks (commas, semicolons, colons, and  so
        on).   This  convention,  sometimes known as "semantic new-
        lines", makes it easier to see the effect of patches, which
        often  operate at the level of individual sentences or sen-
        tence clauses.


Thanks,

Alex

> +mount option (see
> +.BR mount.cifs (8))
> +turns off
> +.BR fnctl (2)
> +and
> +.BR flock ()
> +lock propagation to remote clients and makes
> +.BR flock ()
> +locks advisory again.
>   .SH SEE ALSO
>   .BR flock (1),
>   .BR close (2),
> 

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-03-10 19:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 15:48 [man-pages][PATCH v1] flock.2: add CIFS details Aurélien Aptel
2021-03-03 15:37 ` Tom Talpey
2021-03-03 16:28   ` Aurélien Aptel
2021-03-03 16:37     ` [PATCH v2] " Aurélien Aptel
2021-03-03 18:08       ` Tom Talpey
2021-03-03 19:03         ` [PATCH v3] " Aurélien Aptel
2021-03-03 20:23           ` Tom Talpey
2021-03-04  9:48             ` Aurélien Aptel
2021-03-04  9:50               ` [PATCH v4] " Aurélien Aptel
2021-03-10 19:07                 ` Alejandro Colomar (man-pages) [this message]
2021-03-11 10:11                   ` Aurélien Aptel
2021-03-11 16:21                     ` Tom Talpey
2021-03-11 17:13                       ` Aurélien Aptel
2021-03-11 17:29                         ` Tom Talpey
2021-03-11 17:45                           ` Aurélien Aptel
2021-03-11 20:42                             ` Tom Talpey
2021-03-11 22:39                               ` Aurélien Aptel
2021-03-15 18:05                                 ` Pavel Shilovsky
2021-03-16 10:42                                   ` Aurélien Aptel
2021-03-16 17:39                                     ` Pavel Shilovsky
2021-03-16 19:42                                       ` Tom Talpey
2021-03-16 23:04                                         ` Pavel Shilovsky
2021-03-22 14:30                                           ` [PATCH v5] " Aurélien Aptel
2021-04-09 12:13                                             ` Aurélien Aptel
2021-04-11 19:12                                               ` Alejandro Colomar (man-pages)
2021-03-11 18:01                 ` [PATCH v4] " Matthew Wilcox
2021-03-03 16:48     ` [man-pages][PATCH v1] " Tom Talpey
2021-03-03 16:57       ` Aurélien Aptel
2021-03-03 17:41         ` Tom Talpey

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=45b64990-b879-02d3-28e5-b896af0502c4@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=aaptel@suse.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=smfrench@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.