From: Steve French <smfrench@gmail.com>
To: Jeremy Allison <jra@samba.org>
Cc: Andrew Bartlett <abartlet@samba.org>,
samba-technical <samba-technical@lists.samba.org>,
CIFS <linux-cifs@vger.kernel.org>,
Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: Missing protocol features that could help Linux
Date: Fri, 19 Apr 2024 12:12:04 -0500 [thread overview]
Message-ID: <CAH2r5mvn0tMB_SoQYGh4bVK-ZRYfOLNn4PgX51_rofPkhwqD4g@mail.gmail.com> (raw)
In-Reply-To: <ZiKT4CursWvT2dhq@jeremy-HP-Z840-Workstation>
On Fri, Apr 19, 2024 at 10:55 AM Jeremy Allison <jra@samba.org> wrote:
>
> On Fri, Apr 19, 2024 at 01:40:34PM +1200, Andrew Bartlett wrote:
> >POSIX <-> POSIX locking over SMB is something I have a client trying to
> >get working with SMB3.
> >
> >They have a use case where, as I understand it so far, the mapping of
> >POSIX fcntl() read and write locks to SMB locks isn't 1-1, because they
> >expect advisory locks, but SMB locks are mandatory as far as I read
> >it.
> >
> >They use cifs.ko and Samba, so it isn't about working with Windows, it
> >is about running Libreoffice on LInux against Samba.
>
> That's not going to work the way LibreOffice on Linux expects,
> until we fully expose POSIX locking semantics.
>
> It's the range semantics that will probably break them.
>
> POSIX locks can be split/merged/overlapped. Windows locks
> must be distinct. Currently over SMB3 we only expose Windows
> locks.
For a surprising number of Linux apps mounting with "nobrl" (which only
enforces byte range locks locally, and thus POSIX style not Windows
style) is fine for SMB3.1.1 mounts.
--
Thanks,
Steve
next prev parent reply other threads:[~2024-04-19 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 20:21 Missing protocol features that could help Linux Steve French
2024-04-19 1:40 ` Andrew Bartlett
2024-04-19 15:55 ` Jeremy Allison
2024-04-19 15:58 ` Ralph Boehme
2024-04-19 17:12 ` Steve French [this message]
2024-04-19 16:53 ` Ralph Boehme
2024-04-19 16:55 ` Jeremy Allison
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=CAH2r5mvn0tMB_SoQYGh4bVK-ZRYfOLNn4PgX51_rofPkhwqD4g@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=abartlet@samba.org \
--cc=jra@samba.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).