From: Nick Piggin <npiggin@suse.de>
Date: Tue, 6 Jan 2009 22:39:12 +0000 (-0800)
Subject: mm: do_sync_mapping_range integrity fix
X-Git-Tag: v2.6.28.2~5
X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=34ac6b2ed45605900fa992d5eeee0ba67d0295f0;p=karo-tx-linux.git

mm: do_sync_mapping_range integrity fix

commit ee53a891f47444c53318b98dac947ede963db400 upstream.

Chris Mason notices do_sync_mapping_range didn't actually ask for data
integrity writeout.  Unfortunately, it is advertised as being usable for
data integrity operations.

This is a data integrity bug.

Signed-off-by: Nick Piggin <npiggin@suse.de>
Cc: Chris Mason <chris.mason@oracle.com>
Cc: Dave Chinner <david@fromorbit.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---

diff --git a/fs/sync.c b/fs/sync.c
index 6cc8cb4ac022..9e5f60dbd54b 100644
--- a/fs/sync.c
+++ b/fs/sync.c
@@ -287,7 +287,7 @@ int do_sync_mapping_range(struct address_space *mapping, loff_t offset,
 
 	if (flags & SYNC_FILE_RANGE_WRITE) {
 		ret = __filemap_fdatawrite_range(mapping, offset, endbyte,
-						WB_SYNC_NONE);
+						WB_SYNC_ALL);
 		if (ret < 0)
 			goto out;
 	}