From: "Aurélien Aptel" <aaptel@suse.com>
To: Tom Talpey <tom@talpey.com>,
"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: smfrench@gmail.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: Thu, 11 Mar 2021 18:45:50 +0100 [thread overview]
Message-ID: <878s6ttwhd.fsf@suse.com> (raw)
In-Reply-To: <d602e3e4-721a-a1c5-3375-1c9899da4383@talpey.com>
Tom Talpey <tom@talpey.com> writes:
> and simply state (perhaps)
>
> "Remote and mandatory locking semantics may vary with SMB protocol,
> mount options and server type. See mount.cifs(8) for additional
> information."
This would be the complete addition to the man page? I feel like we
should at least say it is *likely* that:
- locks will be mandatory
- flock() is emulated via fnctl() and so they interact with each other
Which are the 2 aspects that really diverges from the expected behaviour
of flock() and likely to hit people in the wild. Mentionning this will
send people trying to debug their app in the right direction.
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
next prev parent reply other threads:[~2021-03-11 17:46 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)
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 [this message]
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=878s6ttwhd.fsf@suse.com \
--to=aaptel@suse.com \
--cc=alx.manpages@gmail.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.