[ 53/62] eCryptfs: Write out all dirty pages just before releasing the lower file
From: Greg Kroah-Hartman
Date: Thu Oct 18 2012 - 23:11:56 EST
3.4-stable review patch. If anyone has any objections, please let me know.
From: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
commit 7149f2558d5b5b988726662fe58b1c388337805b upstream.
Fixes a regression caused by:
821f749 eCryptfs: Revert to a writethrough cache model
That patch reverted some code (specifically, 32001d6f) that was
necessary to properly handle open() -> mmap() -> close() -> dirty pages
-> munmap(), because the lower file could be closed before the dirty
pages are written out.
Rather than reapplying 32001d6f, this approach is a better way of
ensuring that the lower file is still open in order to handle writing
out the dirty pages. It is called from ecryptfs_release(), while we have
a lock on the lower file pointer, just before the lower file gets the
final fput() and we overwrite the pointer.
Signed-off-by: Tyler Hicks <tyhicks@xxxxxxxxxxxxx>
Reported-by: Artemy Tregubenko <me@xxxxxxxxx>
Tested-by: Artemy Tregubenko <me@xxxxxxxxx>
Tested-by: Colin Ian King <colin.king@xxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
fs/ecryptfs/main.c | 1 +
1 file changed, 1 insertion(+)
@@ -162,6 +162,7 @@ void ecryptfs_put_lower_file(struct inod
inode_info = ecryptfs_inode_to_private(inode);
inode_info->lower_file = NULL;
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/