From: Steve French <smfrench@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: fanotify and network/cluster fs
Date: Wed, 12 May 2021 00:05:25 -0500 [thread overview]
Message-ID: <CAH2r5mvjHcQVCj4g0mNeOHRRjc-xH88XZL-JFSAV+yw=idfMnA@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxigOsEUrU5-QndJujVtP9KLdjEQTm3bHjGRCFWjZCAKBw@mail.gmail.com>
On Mon, May 10, 2021 at 11:34 PM Amir Goldstein <amir73il@gmail.com> wrote:
>
> On Tue, May 11, 2021 at 2:36 AM Steve French <smfrench@gmail.com> wrote:
> >
> > With the recent changes to fanotify (e.g.
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7cea2a3c505e)
>
> Not sure how this is related to remote fs notifications.
>
> > has there been any additional discussion of what it would take to
> > allow fanotify to be supported for network/cluster fs (all major
>
> It would take someone to pick up this RFC that was already posted
> 2 years ago:
> https://lore.kernel.org/linux-fsdevel/20190507085707.GD30899@veci.piliscsaba.redhat.com/
> https://lore.kernel.org/linux-fsdevel/CAOQ4uxipauh1UXHSFt=WsiaDexqecjm4eDkVfnQXN8eYofdg2A@mail.gmail.com/
>
> > dialects supported by cifs.ko support sending notify requests to the
> > server - but there is no way for cifs.ko to be told which notify
> > requests to send as fanotify/inotify are local only in current Linux -
> > unlike other OS where notify is primarily for network fs and passed
> > down to the fs)
> >
>
> If you wait long enough, I'll get to implementing this for FUSE some day...
> But there is *really* nothing blocking cifs developers from implementing this
> and writing the specialized tests. I can help with guidance.
It's on my TODO list but I am dealing with some multichannel bugs at
the moment...
but would be great if someone had run into the same thing and fixed it. If not
I will revisit the question of how to do this
--
Thanks,
Steve
prev parent reply other threads:[~2021-05-12 5:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 23:36 fanotify and network/cluster fs Steve French
2021-05-11 4:33 ` Amir Goldstein
2021-05-12 5:05 ` Steve French [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='CAH2r5mvjHcQVCj4g0mNeOHRRjc-xH88XZL-JFSAV+yw=idfMnA@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=amir73il@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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).