[PATCH] reduce bmv_count in xfs_vn_fiemap

[Olaf Weber]

Eric Sandeen writes:

> commit 6321e3ed2acf3ee9643cdd403e1c88605d7944ba caused
> the full bmv_count's worth of getbmapx structures to get
> allocated; telling it to do MAXEXTNUM was a bit insane,
> resulting in ENOMEM.

> Chop it down to something reasonable, the caller can
> loop over this if the file has > 64 extents.

It does seem to me that this will result in an unusal case for the
caller, in that it will get fewer extents than fit in the provided
buffer, yet should loop.  Do current callers know that they can hit
this case, detect it, and loop accordingly?  Or is this just pushing
the problem/regression to userspace?

> (this is a regression, FWIW)

> Signed-off-by: Eric Sandeen <sandeen at sandeen.net>
> ---

> iff --git a/fs/xfs/linux-2.6/xfs_iops.c b/fs/xfs/linux-2.6/xfs_iops.c
> index 58973bb..370e9a7 100644
> --- a/fs/xfs/linux-2.6/xfs_iops.c
> +++ b/fs/xfs/linux-2.6/xfs_iops.c
> @@ -680,8 +680,12 @@ xfs_vn_fiemap(
>  	else
>  		bm.bmv_length = BTOBB(length);
 
> -	/* our formatter will tell xfs_getbmap when to stop. */
> -	bm.bmv_count = MAXEXTNUM;
> +	/*
> +	 * xfs_getbmap allocates based on that; pick a count that's
> +	 * not too outragous.
> +	 * Our formatter will tell xfs_getbmap when to stop.
> +	 */
> +	bm.bmv_count = 64;
>  	bm.bmv_iflags = BMV_IF_PREALLOC;
>  	if (fieinfo->fi_flags & FIEMAP_FLAG_XATTR)
>  		bm.bmv_iflags |= BMV_IF_ATTRFORK;


-- 
Olaf Weber                 SGI               Phone:  +31(0)30-6696752
                           Veldzigt 2b       Fax:    +31(0)30-6696799
Technical Lead             3454 PW de Meern  Vnet:   955-7151
Storage Software           The Netherlands   Email:  olaf at sgi.com