linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: fanotify and network/cluster fs
Date: Tue, 11 May 2021 07:33:49 +0300	[thread overview]
Message-ID: <CAOQ4uxigOsEUrU5-QndJujVtP9KLdjEQTm3bHjGRCFWjZCAKBw@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5mt1Fy6hR+Rdig0sHsOS8fVQDsKf9HqZjvjORS3R-7=RFw@mail.gmail.com>

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.

Thanks,
Amir.

  reply	other threads:[~2021-05-11  4:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 23:36 Steve French
2021-05-11  4:33 ` Amir Goldstein [this message]
2021-05-12  5:05   ` Steve French

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=CAOQ4uxigOsEUrU5-QndJujVtP9KLdjEQTm3bHjGRCFWjZCAKBw@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --subject='Re: fanotify and network/cluster fs' \
    /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

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).