summaryrefslogtreecommitdiffstats
path: root/fs/ocfs2/alloc.h
diff options
context:
space:
mode:
authorMark Fasheh <mark.fasheh@oracle.com>2007-07-06 14:41:18 -0700
committerMark Fasheh <mark.fasheh@oracle.com>2007-07-10 17:32:07 -0700
commit35edec1d52c075975991471d624b33b9336226f2 (patch)
tree4fc59b9d60826b8eb44bc5c1e558a15bea171193 /fs/ocfs2/alloc.h
parentd0c7d7082ee1ec4f95ee57bf86ed39d1a27c4037 (diff)
downloadop-kernel-dev-35edec1d52c075975991471d624b33b9336226f2.zip
op-kernel-dev-35edec1d52c075975991471d624b33b9336226f2.tar.gz
ocfs2: update truncate handling of partial clusters
The partial cluster zeroing code used during truncate usually assumes that the rightmost byte in the range to be zeroed lies on a cluster boundary. This makes sense for truncate, but punching holes might require zeroing on non-aligned rightmost boundaries. Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
Diffstat (limited to 'fs/ocfs2/alloc.h')
-rw-r--r--fs/ocfs2/alloc.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/ocfs2/alloc.h b/fs/ocfs2/alloc.h
index e3284f3..752ef86 100644
--- a/fs/ocfs2/alloc.h
+++ b/fs/ocfs2/alloc.h
@@ -95,8 +95,8 @@ struct ocfs2_truncate_context {
struct buffer_head *tc_last_eb_bh;
};
-int ocfs2_zero_tail_for_truncate(struct inode *inode, handle_t *handle,
- u64 new_i_size);
+int ocfs2_zero_range_for_truncate(struct inode *inode, handle_t *handle,
+ u64 range_start, u64 range_end);
int ocfs2_prepare_truncate(struct ocfs2_super *osb,
struct inode *inode,
struct buffer_head *fe_bh,
OpenPOWER on IntegriCloud