@@ -37,6 +37,25 @@ ssize_t overlay_read_iter(struct file *file, struct kiocb *kio,
}
EXPORT_SYMBOL(overlay_read_iter);
+int overlay_fsync(struct file *file, loff_t start, loff_t end,
+ int datasync)
+{
+ int ret;
+
+ if (likely(overlay_file_consistent(file)))
+ return file->f_op->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;
+}
+EXPORT_SYMBOL(overlay_fsync);
+
int overlay_mmap(struct file *file, struct vm_area_struct *vma)
{
if (unlikely(!overlay_file_consistent(file))) {
@@ -1748,6 +1748,9 @@ static inline int call_mmap(struct file *file, struct vm_area_struct *vma)
static inline int call_fsync(struct file *file, loff_t start, loff_t end,
int datasync)
{
+ if (unlikely(is_overlay_file(file)))
+ return overlay_fsync(file, start, end, datasync);
+
return file->f_op->fsync(file, start, end, datasync);
}
@@ -11,5 +11,7 @@ struct vm_area_struct;
extern ssize_t overlay_read_iter(struct file *file, struct kiocb *kio,
struct iov_iter *iter);
extern int overlay_mmap(struct file *file, struct vm_area_struct *vma);
+extern int overlay_fsync(struct file *file, loff_t start, loff_t end,
+ int datasync);
#endif /* _LINUX_OVERLAY_FS_H */
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 operation, similarly to read_iter and mmap. Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> --- fs/overlay_util.c | 19 +++++++++++++++++++ include/linux/fs.h | 3 +++ include/linux/overlay_util.h | 2 ++ 3 files changed, 24 insertions(+)