diff options
author | Tao Ma <tao.ma@oracle.com> | 2010-08-30 02:44:03 +0000 |
---|---|---|
committer | Alex Elder <aelder@sgi.com> | 2010-09-03 09:02:11 -0500 |
commit | 9af25465081480a75824fd7a16a37a5cfebeede9 (patch) | |
tree | 475ea0ef9247b65b0ce8997ba581a87bd71c11b6 /.mailmap | |
parent | 23963e54ce187ca6e907c83176c15508b0f6e60d (diff) | |
download | kernel_samsung_tuna-9af25465081480a75824fd7a16a37a5cfebeede9.zip kernel_samsung_tuna-9af25465081480a75824fd7a16a37a5cfebeede9.tar.gz kernel_samsung_tuna-9af25465081480a75824fd7a16a37a5cfebeede9.tar.bz2 |
xfs: Make fiemap work with sparse files
In xfs_vn_fiemap, we set bvm_count to fi_extent_max + 1 and want
to return fi_extent_max extents, but actually it won't work for
a sparse file. The reason is that in xfs_getbmap we will
calculate holes and set it in 'out', while out is malloced by
bmv_count(fi_extent_max+1) which didn't consider holes. So in the
worst case, if 'out' vector looks like
[hole, extent, hole, extent, hole, ... hole, extent, hole],
we will only return half of fi_extent_max extents.
This patch add a new parameter BMV_IF_NO_HOLES for bvm_iflags.
So with this flags, we don't use our 'out' in xfs_getbmap for
a hole. The solution is a bit ugly by just don't increasing
index of 'out' vector. I felt that it is not easy to skip it
at the very beginning since we have the complicated check and
some function like xfs_getbmapx_fix_eof_hole to adjust 'out'.
Cc: Dave Chinner <david@fromorbit.com>
Signed-off-by: Tao Ma <tao.ma@oracle.com>
Signed-off-by: Alex Elder <aelder@sgi.com>
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions