xfs
[Top] [All Lists]

Re: [PATCH 3/9] xfs: correctly decrement the extent buffer index in xfs_

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [PATCH 3/9] xfs: correctly decrement the extent buffer index in xfs_bmap_del_extent
From: Alex Elder <aelder@xxxxxxx>
Date: Tue, 24 May 2011 19:27:14 -0500
Cc: <xfs@xxxxxxxxxxx>
In-reply-to: <20110511150711.786279651@xxxxxxxxxxxxxxxxxxxxxx>
References: <20110511150402.258164661@xxxxxxxxxxxxxxxxxxxxxx> <20110511150711.786279651@xxxxxxxxxxxxxxxxxxxxxx>
Reply-to: <aelder@xxxxxxx>
On Wed, 2011-05-11 at 11:04 -0400, Christoph Hellwig wrote:
> plain text document attachment (xfs-fix-ep-access)
> The code in xfs_bmap_del_extent does not correctly decrement the extent buffer
> index when deleting a whole extent.  Most of the time this gets caught by
> checks in xfs_bmapi that work around it and decrement it manually and thus
> wasn't noticed so far.
> 
> Based on an earlier patch from Lachlan McIlroy.
> 
> Signed-off-by: Christoph Hellwig <hch@xxxxxx>

This one crashes in test 008.  I suspect it's due to
what Lachlan pointed out--the index can go negative
and we aren't (yet) ensuring we don't call into
xfs_iext_get_ext() in that case--but I have not
absolutely verified this.

It would be better if this change were combined
with the portion of patch 6 that pulls out the
    if (lastx >= XFS_IFORK_NEXTENTS()
check in xfs_bunmapi().  But it still would
need to go later in the series.

This does look like it's a reasonable thing to do,
it moves "left" in extent list because we know
we've exhausted the current one, and the only
caller--xfs_bunmapi()--is going from the end
backward.  I think the same decrement would be
appropriate for "case 2" below where you put this
change though (because there will be no more of
the current extent remaining after deleting the
left portion).  In fact, it looks to me like
the only one that got it right was "case 1"
because if you're splitting an extent (case 0)
the next one to examine will be the left one
of the two resulting from the split.  (I'm a
bit unsure about these observations though,
you or someone else should verify this and
set me straight if I'm wrong.)

It's all a bit confusing though.  It's not
obvious here what the value of *idx should be
after one of these operations, certainly not
independent of knowledge of whether the
extents are being scanned from the beginning
(as xfs_bmapi() does) or from the end (as
xfs_bunmap() does).


I moved this one change to the end of the series
and I no longer hit the problem I had with test
008 (presumably because the index checking in
later patches avoids the problem).  I will
keep testing with the whole series, with
this one at the end.

Meanwhile I'm interested to hear back on
whether other spots in xfs_bmap_del_extent()
should adjust the index value.

                                        -Alex



> Index: xfs/fs/xfs/xfs_bmap.c
> ===================================================================
> --- xfs.orig/fs/xfs/xfs_bmap.c        2011-05-10 17:11:21.212901236 +0200
> +++ xfs/fs/xfs/xfs_bmap.c     2011-05-10 17:13:36.177399627 +0200
> @@ -2916,8 +2916,10 @@ xfs_bmap_del_extent(
>                */
>               xfs_iext_remove(ip, *idx, 1,
>                               whichfork == XFS_ATTR_FORK ? BMAP_ATTRFORK : 0);
> +             --*idx;
>               if (delay)
>                       break;
> +
>               XFS_IFORK_NEXT_SET(ip, whichfork,
>                       XFS_IFORK_NEXTENTS(ip, whichfork) - 1);
>               flags |= XFS_ILOG_CORE;
> 
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs



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