From: Miklos Szeredi <miklos@szeredi.hu>
To: Sargun Dhillon <sargun@sargun.me>
Cc: Amir Goldstein <amir73il@gmail.com>,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH] overlay: Plumb through flush method
Date: Wed, 20 Jan 2021 16:24:40 +0100 [thread overview]
Message-ID: <CAJfpeguLFoLD8BYuNAAwV+F0583aujNBqto3QnFjeV+z4LszDA@mail.gmail.com> (raw)
In-Reply-To: <CAMp4zn9sdpk1A1hYpDjS_774UscYZ1sztCsLdfshs=pXEYf0NQ@mail.gmail.com>
On Thu, Dec 3, 2020 at 7:32 PM Sargun Dhillon <sargun@sargun.me> wrote:
>
> On Thu, Dec 3, 2020 at 2:32 AM Amir Goldstein <amir73il@gmail.com> wrote:
> >
> > On Thu, Dec 3, 2020 at 12:16 PM Sargun Dhillon <sargun@sargun.me> wrote:
> > >
> > > On Sun, Nov 29, 2020 at 7:00 PM Sargun Dhillon <sargun@sargun.me> wrote:
> > > >
> > > > Filesystems can implement their own flush method that release
> > > > resources, or manipulate caches. Currently if one of these
> > > > filesystems is used with overlayfs, the flush method is not called.
> > > >
> > > > Signed-off-by: Sargun Dhillon <sargun@sargun.me>
> > > > Cc: linux-fsdevel@vger.kernel.org
> > > > Cc: linux-unionfs@vger.kernel.org
> > > > Cc: Miklos Szeredi <miklos@szeredi.hu>
> > > > Cc: Amir Goldstein <amir73il@gmail.com>
> > > > ---
> > > > fs/overlayfs/file.c | 11 +++++++++++
> > > > 1 file changed, 11 insertions(+)
> > > >
> > > > diff --git a/fs/overlayfs/file.c b/fs/overlayfs/file.c
> > > > index efccb7c1f9bc..802259f33c28 100644
> > > > --- a/fs/overlayfs/file.c
> > > > +++ b/fs/overlayfs/file.c
> > > > @@ -787,6 +787,16 @@ static loff_t ovl_remap_file_range(struct file *file_in, loff_t pos_in,
> > > > remap_flags, op);
> > > > }
> > > >
> > > > +static int ovl_flush(struct file *file, fl_owner_t id)
> > > > +{
> > > > + struct file *realfile = file->private_data;
> > > > +
> > > > + if (realfile->f_op->flush)
> > > > + return realfile->f_op->flush(realfile, id);
> > > > +
> > > > + return 0;
> > > > +}
> > > > +
> > > > const struct file_operations ovl_file_operations = {
> > > > .open = ovl_open,
> > > > .release = ovl_release,
> > > > @@ -798,6 +808,7 @@ const struct file_operations ovl_file_operations = {
> > > > .fallocate = ovl_fallocate,
> > > > .fadvise = ovl_fadvise,
> > > > .unlocked_ioctl = ovl_ioctl,
> > > > + .flush = ovl_flush,
> > > > #ifdef CONFIG_COMPAT
> > > > .compat_ioctl = ovl_compat_ioctl,
> > > > #endif
> > > > --
> > > > 2.25.1
> > > >
> > >
> > > Amir, Miklos,
> > > Is this acceptable? I discovered this being a problem when we had the discussion
> > > of whether the volatile fs should return an error on close on dirty files.
> >
> > Yes, looks ok.
> > Maybe we want to check if the realfile is upper although
> > maybe flush can release resources also on read only fs?
> >
> > >
> > > It seems like it would be useful if anyone uses NFS, or CIFS as an upperdir.
> >
> > They are not supported as upperdir. only FUSE is.
> >
> > Thanks,
> > Amir.
>
> VFS does it on read-only files / mounts, so we should probably do the
> same thing.
Right, but it should handle files copied up after the oipen (i.e. call
ovl_real_fdget() to get the real file).
Thanks,
Miklos
next prev parent reply other threads:[~2021-01-20 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 3:00 [PATCH] overlay: Plumb through flush method Sargun Dhillon
2020-12-03 10:16 ` Sargun Dhillon
2020-12-03 10:32 ` Amir Goldstein
2020-12-03 18:32 ` Sargun Dhillon
2021-01-20 15:24 ` Miklos Szeredi [this message]
2021-01-23 12:54 ` Amir Goldstein
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=CAJfpeguLFoLD8BYuNAAwV+F0583aujNBqto3QnFjeV+z4LszDA@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=sargun@sargun.me \
/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).