public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lachlan McIlroy <lachlan@sgi.com>
To: tes@sgi.com
Cc: xfs-dev@sgi.com, xfs@oss.sgi.com
Subject: Re: [PATCH] fix up delta calculation for xfs_bmap_add_extent_unwritten_real
Date: Tue, 15 Jul 2008 12:43:25 +1000	[thread overview]
Message-ID: <487C0ECD.5050205@sgi.com> (raw)
In-Reply-To: <487afa7f.JM4ZHhEHVRIFNZ+O%tes@sgi.com>

Looks good to me.

I can't understand why this code is inconsistent with the other cases
- no other cases adjusts PREV or the cursor (other than the state).
To be consistent it would update PREV to become the new LHS by passing
'new->br_startoff - PREV.br_startoff' into xfs_bmbt_update() and then
inserting r[0] and r[1] although that way would require an extra call
to xfs_bmbt_increment().

tes@sgi.com wrote:
> pv#984030
> Patch provided by olaf@sgi.com and has been reviewed
> but putting out there for others to see the change.
> 
> A bug was found in xfs_bmap_add_extent_unwritten_real() which will
> not affect xfs in its normal use.
> In a particular case, the delta param which is supposed to describe
> the region where extents have changed was not updated appropriately.
> 
> The case of interest is:
>    1707         case 0:
>    1708                 /*
>    1709                  * Setting the middle part of a previous oldext extent to
>    1710                  * newext.  Contiguity is impossible here.
>    1711                  * One extent becomes three extents.
>    1712                  */
> 
> where we are not left-filling (on LHS) or right-filling (on RHS) and so
> are also not contiguous with neighbours. But we are in the middle.
> 
> PREV:------------------------------------------------------------>|
> -----------------------|--------------------|----------------------
> |  cur->bc_rec.b  LHS  |    r[0] = new      |    r[1] RHS         |
> -----------------------|--------------------|----------------------
> 
> So our new extent is in the middle and r[1] is on the RHS.
> The LHS, cur, is set to PREV after making PREV's count smaller
> to its new size. However, this means that our original PREV's count
> is no longer covering the whole range.
> So Olaf's change leave's PREV alone and just updates cur->bc_rec.b to have
> PREV's contents and decrements its new count.
> Mainly, because below we calculate the delta based on the PREV values
> (in particular expecting the original block count).
> We are not using PREV anywhere else after that AFAICS so I think the
> change is safe from causing a regression elsewhere.
> 
> --Tim
> 
>  xfs_bmap.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> Index: 2.6.x-xfs-quilt/fs/xfs/xfs_bmap.c
> ===================================================================
> --- 2.6.x-xfs-quilt.orig/fs/xfs/xfs_bmap.c	2008-07-04 15:34:38.000000000 +1000
> +++ 2.6.x-xfs-quilt/fs/xfs/xfs_bmap.c	2008-07-09 16:24:17.250532483 +1000
> @@ -1740,9 +1740,9 @@ xfs_bmap_add_extent_unwritten_real(
>  				r[1].br_state)))
>  				goto done;
>  			/* new left extent - oldext */
> -			PREV.br_blockcount =
> -				new->br_startoff - PREV.br_startoff;
>  			cur->bc_rec.b = PREV;
> +			cur->bc_rec.b.br_blockcount =
> +				new->br_startoff - PREV.br_startoff;
>  			if ((error = xfs_bmbt_insert(cur, &i)))
>  				goto done;
>  			XFS_WANT_CORRUPTED_GOTO(i == 1, done);
> 
> 
> 

      reply	other threads:[~2008-07-15  2:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14  7:04 [PATCH] fix up delta calculation for xfs_bmap_add_extent_unwritten_real tes
2008-07-15  2:43 ` Lachlan McIlroy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=487C0ECD.5050205@sgi.com \
    --to=lachlan@sgi.com \
    --cc=tes@sgi.com \
    --cc=xfs-dev@sgi.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox