From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759424Ab3EWVcs (ORCPT ); Thu, 23 May 2013 17:32:48 -0400 Received: from mail-vb0-f74.google.com ([209.85.212.74]:61046 "EHLO mail-vb0-f74.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759190Ab3EWVcr (ORCPT ); Thu, 23 May 2013 17:32:47 -0400 From: Paul Taysom To: Tyler Hicks Cc: Dustin Kirkland , ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org, olofj@chromium.org, taysom@chromium.org Subject: [PATCH] fs: ecryptfs: fixed msync to flush data Date: Thu, 23 May 2013 14:31:43 -0700 Message-Id: <1369344703-22245-1-git-send-email-taysom@chromium.org> X-Mailer: git-send-email 1.8.2.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When msync is called on a memory mapped file, that data is not flushed to the disk. In Linux, msync calls fsync for the file. For ecryptfs, fsync just calls the lower level file system's fsync. Changed the ecryptfs fsync code to call filemap_write_and_wait before calling the lower level fsync. Addresses the problem described in http://crbug.com/239536 Signed-off-by: Paul Taysom --- fs/ecryptfs/file.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/ecryptfs/file.c b/fs/ecryptfs/file.c index 201f0a0..16f509d 100644 --- a/fs/ecryptfs/file.c +++ b/fs/ecryptfs/file.c @@ -295,6 +295,7 @@ static int ecryptfs_release(struct inode *inode, struct file *file) static int ecryptfs_fsync(struct file *file, loff_t start, loff_t end, int datasync) { + filemap_write_and_wait(file->f_mapping); return vfs_fsync(ecryptfs_file_to_lower(file), datasync); } -- 1.8.2.1