Treat writes as new when holes span across page boundaries
authorGoldwyn Rodrigues <rgoldwyn@gmail.com>
Thu, 17 Feb 2011 15:44:40 +0000 (09:44 -0600)
committerBrad Figg <brad.figg@canonical.com>
Wed, 27 Apr 2011 18:41:16 +0000 (11:41 -0700)
commit7964c982700a55bcbd5757313d5abbe43d81229a
tree44fa7ffd2e8edc01ebba2d6405d898cebbfa3a18
parentc6486bb3d4a8bacae9e31fbfcc555f611626a37b
Treat writes as new when holes span across page boundaries

BugLink: http://bugs.launchpad.net/bugs/761134

commit 272b62c1f0f6f742046e45b50b6fec98860208a0 upstream.

When a hole spans across page boundaries, the next write forces
a read of the block. This could end up reading existing garbage
data from the disk in ocfs2_map_page_blocks. This leads to
non-zero holes. In order to avoid this, mark the writes as new
when the holes span across page boundaries.

Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.de>
Signed-off-by: jlbec <jlbec@evilplan.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
fs/ocfs2/aops.c