xfs: reduce bmv_count in xfs_vn_fiemap
authorEric Sandeen <sandeen@sandeen.net>
Mon, 27 Jul 2009 02:52:01 +0000 (21:52 -0500)
committerFelix Blyakher <felixb@sgi.com>
Fri, 31 Jul 2009 05:56:58 +0000 (00:56 -0500)
commit97db39a1f6f69e906e98118392400de5217aa33a
treef5735b99542d8d31dcad907294c5cf7a0657b563
parentfd40261354802b0f05f6f67121235aa002e87069
xfs: reduce bmv_count in xfs_vn_fiemap

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 every time.

Chop it down to something reasonable, the number of slots
in the caller's input buffer.  If this is too large the
caller may get ENOMEM but the reason should not be a
mystery, and they can try again with something smaller.

We add 1 to the value because in the normal getbmap
world, bmv_count includes the header and xfs_getbmap does:

        nex = bmv->bmv_count - 1;
        if (nex <= 0)
                return XFS_ERROR(EINVAL);

Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Reviewed-by: Olaf Weber <olaf@sgi.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Felix Blyakher <felixb@sgi.com>
fs/xfs/linux-2.6/xfs_iops.c