diff options
author | Nick Piggin <npiggin@suse.de> | 2009-01-06 17:39:12 -0500 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-01-06 18:59:00 -0500 |
commit | ee53a891f47444c53318b98dac947ede963db400 (patch) | |
tree | 57cec3b7aadb120b5a2857bd212159a693a379f2 /fs | |
parent | 82fd1a9a8ced9607312b54859572bcc6211e8919 (diff) |
mm: do_sync_mapping_range integrity fix
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>
Diffstat (limited to 'fs')
-rw-r--r-- | fs/sync.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -295,7 +295,7 @@ int do_sync_mapping_range(struct address_space *mapping, loff_t offset, | |||
295 | 295 | ||
296 | if (flags & SYNC_FILE_RANGE_WRITE) { | 296 | if (flags & SYNC_FILE_RANGE_WRITE) { |
297 | ret = __filemap_fdatawrite_range(mapping, offset, endbyte, | 297 | ret = __filemap_fdatawrite_range(mapping, offset, endbyte, |
298 | WB_SYNC_NONE); | 298 | WB_SYNC_ALL); |
299 | if (ret < 0) | 299 | if (ret < 0) |
300 | goto out; | 300 | goto out; |
301 | } | 301 | } |