From: Miklos Szeredi <mszeredi@redhat.com>
To: linux-unionfs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 7/7] ovl: intercept fsync
Date: Thu, 24 Nov 2016 11:55:44 +0100 [thread overview]
Message-ID: <1479984944-1017-9-git-send-email-mszeredi@redhat.com> (raw)
In-Reply-To: <1479984944-1017-1-git-send-email-mszeredi@redhat.com>
Fsync is really an inode operation (AFAICS) so a doing it on a O_RDONLY
file descriptor should flush any data written through an O_WRONLY file
descriptor for example.
To make this work correctly in case the file is copied up after being
opened for read intercept the fsync fop, similarly to read_iter and mmap.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
---
fs/overlayfs/inode.c | 23 ++++++++++++++++++++---
1 file changed, 20 insertions(+), 3 deletions(-)
diff --git a/fs/overlayfs/inode.c b/fs/overlayfs/inode.c
index 25b31c6ebe9e..f522cb350f3c 100644
--- a/fs/overlayfs/inode.c
+++ b/fs/overlayfs/inode.c
@@ -412,6 +412,24 @@ static int ovl_mmap(struct file *file, struct vm_area_struct *vma)
return file->f_op->mmap(file, vma);
}
+static int ovl_fsync(struct file *file, loff_t start, loff_t end, int datasync)
+{
+ int ret;
+
+ if (likely(ovl_file_is_lower(file))) {
+ return OVL_CALL_REAL_FOP(file,
+ fsync(file, start, end, datasync));
+ }
+ file = filp_clone_open(file);
+ if (IS_ERR(file))
+ return PTR_ERR(file);
+
+ ret = vfs_fsync_range(file, start, end, datasync);
+ fput(file);
+
+ return ret;
+}
+
static struct ovl_fops *ovl_fops_find(const struct file_operations *orig)
{
struct ovl_fops *ofop;
@@ -453,9 +471,8 @@ static struct ovl_fops *ovl_fops_get(struct file *file)
ofop->fops.read_iter = ovl_read_iter;
if (orig->mmap)
ofop->fops.mmap = ovl_mmap;
-
- /* These will need to be intercepted: */
- ofop->fops.fsync = orig->fsync;
+ if (orig->fsync)
+ ofop->fops.fsync = ovl_fsync;
/*
* These should be intercepted, but they are very unlikely to be
--
2.5.5
prev parent reply other threads:[~2016-11-24 11:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 10:55 [PATCH 0/7] overlayfs: fix ro/rw fd data inconsistecies Miklos Szeredi
2016-11-24 10:55 ` Miklos Szeredi
2016-11-24 14:14 ` Miklos Szeredi
2016-11-24 20:50 ` Amir Goldstein
2016-11-24 10:55 ` [PATCH 1/7] vfs: allow overlayfs to intercept file ops Miklos Szeredi
2016-11-24 10:55 ` [PATCH 2/7] vfs: export filp_clone_open() Miklos Szeredi
2016-11-24 10:55 ` [PATCH 3/7] mm: ovl: copy-up on MAP_SHARED Miklos Szeredi
2016-11-25 21:20 ` [mm] 68ab21008a: BUG:unable_to_handle_kernel kernel test robot
2016-11-24 10:55 ` [PATCH 4/7] ovl: add infrastructure for intercepting file ops Miklos Szeredi
2016-11-24 11:52 ` Amir Goldstein
2016-11-24 12:03 ` Miklos Szeredi
2016-11-24 13:12 ` Amir Goldstein
2016-11-24 13:51 ` Miklos Szeredi
2016-11-24 14:08 ` Amir Goldstein
2016-11-25 5:22 ` Amir Goldstein
2016-11-24 10:55 ` [PATCH 5/7] ovl: intercept read_iter Miklos Szeredi
2016-11-24 10:55 ` [PATCH 6/7] ovl: intercept mmap Miklos Szeredi
2016-11-24 13:25 ` Amir Goldstein
2016-11-24 18:03 ` Amir Goldstein
2016-11-24 19:06 ` Amir Goldstein
2016-11-24 10:55 ` Miklos Szeredi [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=1479984944-1017-9-git-send-email-mszeredi@redhat.com \
--to=mszeredi@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@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
Powered by JetHome