From mboxrd@z Thu Jan  1 00:00:00 1970
From: npiggin@suse.de
Subject: [patch 3/7] mm: do_sync_mapping_range integrity fix
Date: Tue, 21 Oct 2008 19:09:50 +1100
Message-ID: <20081021081138.983141000@nick.local0.net>
References: <20081021080947.032757000@suse.de>
Cc: linux-fsdevel@vger.kernel.org
To: akpm@linux-foundation.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from ns1.suse.de ([195.135.220.2]:54010 "EHLO mx1.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751561AbYJUIP1 (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 21 Oct 2008 04:15:27 -0400
Content-Disposition: inline; filename=mm-do-sync-mapping-range-fix.patch
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

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 interity bug.

Signed-off-by: Nick Piggin <npiggin@suse.de>
---
Index: linux-2.6/fs/sync.c
===================================================================
--- linux-2.6.orig/fs/sync.c
+++ linux-2.6/fs/sync.c
@@ -269,7 +269,7 @@ int do_sync_mapping_range(struct address
 
 	if (flags & SYNC_FILE_RANGE_WRITE) {
 		ret = __filemap_fdatawrite_range(mapping, offset, endbyte,
-						WB_SYNC_NONE);
+						WB_SYNC_ALL);
 		if (ret < 0)
 			goto out;
 	}

--