From: Jeff Layton <jlayton@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>, Amir Goldstein <amir73il@gmail.com>
Cc: Bernd Schubert <bernd.schubert@fastmail.fm>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fuse: allow FUSE drivers to declare themselves free from outside changes
Date: Tue, 02 Apr 2024 10:51:45 -0400 [thread overview]
Message-ID: <fbd0b9e5fb765eaea98fef23e9e36f266d7926ea.camel@kernel.org> (raw)
In-Reply-To: <CAJfpegvRDKS1kKrMPyqzmuSs8KXZ2ohpwp0nEzEf7e3vv940xg@mail.gmail.com>
On Tue, 2024-04-02 at 16:38 +0200, Miklos Szeredi wrote:
> On Tue, 2 Apr 2024 at 16:02, Amir Goldstein <amir73il@gmail.com> wrote:
> >
> > On Tue, Apr 2, 2024 at 4:29 PM Jeff Layton <jlayton@kernel.org> wrote:
> > >
> > > On Tue, 2024-04-02 at 15:23 +0200, Bernd Schubert wrote:
>
> > > > Could you please add something like below?
> > > >
> > > > FUSE_NO_OUTSIDE_CHANGES: No file changes through other mounts / clients
> > > >
>
> "through other mounts" is confusing, since one instance of the fuse
> filesystem can have many mounts, and changes can be done through all
> of them. The issue is if changes are spontaneous from the viewpoint
> of the fuse client.
>
I'm fine with whatever verbiage you prefer. Let me know if you need me
to resend.
> > >
> > > Definitely. I've added that in my local branch. I can either resend
> > > later, or maybe Miklos can just add that if he's otherwise OK with this
> > > patch.
> >
> > Don't love the name but don't have any suggestions either.
> >
> > I am wondering out loud, if we have such a mode for the fs,
> > if and how should it affect caching configuration?
Another thing to consider: what about fsnotify? Should notifications be
allowed when this flag isn't set?
>
> IMO it should enable all caching and override any conflicting options.
> That's a separate patch, but should be done within the next cycle.
> I'll look into that.
>
Thanks!
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-04-02 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 13:10 [PATCH v2] fuse: allow FUSE drivers to declare themselves free from outside changes Jeff Layton
2024-04-02 13:23 ` Bernd Schubert
2024-04-02 13:27 ` Jeff Layton
2024-04-02 14:02 ` Amir Goldstein
2024-04-02 14:38 ` Miklos Szeredi
2024-04-02 14:51 ` Jeff Layton [this message]
2024-04-02 14:54 ` Miklos Szeredi
2024-04-02 14:57 ` Jeff Layton
2024-04-02 14:49 ` Christoph Hellwig
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=fbd0b9e5fb765eaea98fef23e9e36f266d7926ea.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=amir73il@gmail.com \
--cc=bernd.schubert@fastmail.fm \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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