public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/8] xfs: move some code around inside xfs_bmap_shift_extents
Date: Tue, 29 Aug 2017 12:35:11 -0700	[thread overview]
Message-ID: <20170829193511.GE4757@magnolia> (raw)
In-Reply-To: <20170829174835.2218-5-hch@lst.de>

On Tue, Aug 29, 2017 at 07:48:31PM +0200, Christoph Hellwig wrote:
> For the first right move we need to look up next_fsb.  That means
> our last fsb that contains next_fsb must also be the current extent,
> so take advantage of that by moving the code around a bit.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Looks ok, will test...
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

Though I gotta ask, for the cases where we check current_ext against
stop_extent and return -EIO, isn't that only possible if there's
something seriously wrong with the extent map?  In which case
-EFSCORRUPTED might be a more appropriate choice?

(Separate fix, obviously...)

--D

> ---
>  fs/xfs/libxfs/xfs_bmap.c | 54 ++++++++++++++++++++++++++----------------------
>  1 file changed, 29 insertions(+), 25 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c
> index c944987c485d..6af3cc1fc630 100644
> --- a/fs/xfs/libxfs/xfs_bmap.c
> +++ b/fs/xfs/libxfs/xfs_bmap.c
> @@ -6127,7 +6127,6 @@ xfs_bmap_shift_extents(
>  	ASSERT(xfs_isilocked(ip, XFS_IOLOCK_EXCL));
>  	ASSERT(xfs_isilocked(ip, XFS_ILOCK_EXCL));
>  	ASSERT(direction == SHIFT_LEFT || direction == SHIFT_RIGHT);
> -	ASSERT(*next_fsb != NULLFSBLOCK || direction == SHIFT_RIGHT);
>  
>  	ifp = XFS_IFORK_PTR(ip, whichfork);
>  	if (!(ifp->if_flags & XFS_IFEXTENTS)) {
> @@ -6159,43 +6158,48 @@ xfs_bmap_shift_extents(
>  	 * In case of first right shift, we need to initialize next_fsb
>  	 */
>  	if (*next_fsb == NULLFSBLOCK) {
> -		gotp = xfs_iext_get_ext(ifp, total_extents - 1);
> +		ASSERT(direction == SHIFT_RIGHT);
> +
> +		current_ext = total_extents - 1;
> +		gotp = xfs_iext_get_ext(ifp, current_ext);
>  		xfs_bmbt_get_all(gotp, &got);
>  		*next_fsb = got.br_startoff;
>  		if (stop_fsb > *next_fsb) {
>  			*done = 1;
>  			goto del_cursor;
>  		}
> +	} else {
> +		/*
> +		 * Look up the extent index for the fsb where we start shifting. We can
> +		 * henceforth iterate with current_ext as extent list changes are locked
> +		 * out via ilock.
> +		 *
> +		 * gotp can be null in 2 cases: 1) if there are no extents or 2)
> +		 * *next_fsb lies in a hole beyond which there are no extents. Either
> +		 * way, we are done.
> +		 */
> +		gotp = xfs_iext_bno_to_ext(ifp, *next_fsb, &current_ext);
> +		if (!gotp) {
> +			*done = 1;
> +			goto del_cursor;
> +		}
>  	}
>  
>  	/* Lookup the extent index at which we have to stop */
>  	if (direction == SHIFT_RIGHT) {
> -		gotp = xfs_iext_bno_to_ext(ifp, stop_fsb, &stop_extent);
> +		xfs_iext_bno_to_ext(ifp, stop_fsb, &stop_extent);
>  		/* Make stop_extent exclusive of shift range */
>  		stop_extent--;
> -	} else
> +		if (current_ext <= stop_extent) {
> +			error = -EIO;
> +			goto del_cursor;
> +		}
> +	} else {
>  		stop_extent = total_extents;
> -
> -	/*
> -	 * Look up the extent index for the fsb where we start shifting. We can
> -	 * henceforth iterate with current_ext as extent list changes are locked
> -	 * out via ilock.
> -	 *
> -	 * gotp can be null in 2 cases: 1) if there are no extents or 2)
> -	 * *next_fsb lies in a hole beyond which there are no extents. Either
> -	 * way, we are done.
> -	 */
> -	gotp = xfs_iext_bno_to_ext(ifp, *next_fsb, &current_ext);
> -	if (!gotp) {
> -		*done = 1;
> -		goto del_cursor;
> -	}
> -
> -	/* some sanity checking before we finally start shifting extents */
> -	if ((direction == SHIFT_LEFT && current_ext >= stop_extent) ||
> -	     (direction == SHIFT_RIGHT && current_ext <= stop_extent)) {
> -		error = -EIO;
> -		goto del_cursor;
> +		if (current_ext >= stop_extent) {
> +			error = -EIO;
> +			goto del_cursor;
> +		}
>  	}
>  
>  	while (nexts++ < num_exts) {
> -- 
> 2.11.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-08-29 19:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 17:48 a few extent lookup cleanups Christoph Hellwig
2017-08-29 17:48 ` [PATCH 1/8] xfs: add a xfs_iext_update_extent helper Christoph Hellwig
2017-08-29 18:09   ` Darrick J. Wong
2017-08-29 17:48 ` [PATCH 2/8] xfs: switch xfs_bmap_local_to_extents to use xfs_iext_insert Christoph Hellwig
2017-08-29 18:13   ` Darrick J. Wong
2017-08-29 17:48 ` [PATCH 3/8] xfs: use xfs_iext_get_extent in xfs_bmap_first_unused Christoph Hellwig
2017-08-29 18:41   ` Darrick J. Wong
2017-09-01 20:06     ` Christoph Hellwig
2017-09-01 20:08       ` Darrick J. Wong
2017-08-29 17:48 ` [PATCH 4/8] xfs: move some code around inside xfs_bmap_shift_extents Christoph Hellwig
2017-08-29 19:35   ` Darrick J. Wong [this message]
2017-08-29 17:48 ` [PATCH 5/8] xfs: use xfs_iext_*_extent helpers in xfs_bmap_shift_extents Christoph Hellwig
2017-08-30  0:05   ` Darrick J. Wong
2017-08-30 23:03     ` Darrick J. Wong
2017-08-29 17:48 ` [PATCH 6/8] xfs: use xfs_iext_*_extent helpers in xfs_bmap_split_extent_at Christoph Hellwig
2017-08-29 18:42   ` Darrick J. Wong
2017-08-29 17:48 ` [PATCH 7/8] xfs: rewrite xfs_bmap_count_leaves using xfs_iext_get_extent Christoph Hellwig
2017-08-29 18:43   ` Darrick J. Wong
2017-08-29 17:48 ` [PATCH 8/8] xfs: replace xfs_qm_get_rtblks with a direct call to xfs_bmap_count_leaves Christoph Hellwig
2017-08-29 18:44   ` Darrick J. Wong
2017-08-30 23:10 ` [PATCH 9/8] xfs: simplify the rmap code in xfs_bmse_merge Darrick J. Wong
2017-08-31 13:31   ` Christoph Hellwig

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=20170829193511.GE4757@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    /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