From: Ralph Boehme <slow@samba.org>
To: Amir Goldstein <amir73il@gmail.com>, Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
samba-technical <samba-technical@lists.samba.org>,
LKML <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Ioannis Angelakopoulos <jaggel@bu.edu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
lsf-pc <lsf-pc@lists.linux-foundation.org>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] Enabling change notification for network and cluster fs
Date: Mon, 28 Feb 2022 06:42:36 +0100 [thread overview]
Message-ID: <d1b3419e-886c-d479-0c43-b4e64e5465a8@samba.org> (raw)
In-Reply-To: <CAOQ4uxi+VJG56TPvcpOqoVAGgbb8gZQJEfvhXyGyB5VboRE2wA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 332 bytes --]
Hi Amir,
On 2/26/22 11:22, Amir Goldstein wrote:
> I guess SMB protocol does not allow client B to request a NOTIFY on change
> when client A has a directory lease, because requesting NOTIFY requires
> getting a read file handle on the dir?
fwiw, you don't get a "W" SMB3 directory lease, so this is not a problem.
-slow
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-02-28 5:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 5:16 [LSF/MM/BPF TOPIC] Enabling change notification for network and cluster fs Steve French
2022-02-24 21:52 ` Vivek Goyal
2022-02-24 22:55 ` Steve French
2022-02-25 13:23 ` Vivek Goyal
2022-02-25 13:49 ` Matthew Wilcox
2022-02-25 14:30 ` Vivek Goyal
2022-02-25 15:27 ` Steve French
2022-02-25 16:35 ` Vivek Goyal
[not found] ` <CAH2r5msPz1JZK4OWX_=+2HTzKTZE07ACxbEv3xM-1T0HTnVWMw@mail.gmail.com>
2022-02-26 10:22 ` [Lsf-pc] " Amir Goldstein
2022-02-28 5:42 ` Ralph Boehme [this message]
2022-02-26 16:44 ` Vivek Goyal
2022-03-11 12:36 ` Vivek Goyal
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=d1b3419e-886c-d479-0c43-b4e64e5465a8@samba.org \
--to=slow@samba.org \
--cc=amir73il@gmail.com \
--cc=jaggel@bu.edu \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=vgoyal@redhat.com \
--cc=willy@infradead.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 NNTP newsgroup(s).