[Top] [All Lists]

Re: [PATCH] reduce bmv_count in xfs_vn_fiemap

To: Olaf Weber <olaf@xxxxxxx>
Subject: Re: [PATCH] reduce bmv_count in xfs_vn_fiemap
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Thu, 16 Jul 2009 09:19:42 -0500
Cc: xfs mailing list <xfs@xxxxxxxxxxx>
In-reply-to: <bzybpnkhp62.fsf@xxxxxxxxxxxxxxxxxxxx>
References: <4A5E2F01.7030107@xxxxxxxxxxx> <bzybpnkhp62.fsf@xxxxxxxxxxxxxxxxxxxx>
User-agent: Thunderbird (Macintosh/20090605)
Olaf Weber wrote:
> 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?

Well, userspace just keeps calling until it gets FIEMAP_LAST in the
flags.  But yeah, I forgot that we were given the nr of user extents,
I'll send a better V2.


<Prev in Thread] Current Thread [Next in Thread>