public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, edwin@etorok.net
Subject: Re: [PATCH 6/9] xfs: reflink can skip remap existing mappings
Date: Thu, 25 Jun 2020 08:28:18 -0400	[thread overview]
Message-ID: <20200625122818.GH2863@bfoster> (raw)
In-Reply-To: <159304789856.874036.15102270304208951038.stgit@magnolia>

On Wed, Jun 24, 2020 at 06:18:18PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
> 
> If the source and destination map are identical, we can skip the remap
> step to save some time.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
>  fs/xfs/xfs_reflink.c |   17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 
> 
> diff --git a/fs/xfs/xfs_reflink.c b/fs/xfs/xfs_reflink.c
> index 72de7179399d..f1156f121b7d 100644
> --- a/fs/xfs/xfs_reflink.c
> +++ b/fs/xfs/xfs_reflink.c
> @@ -1031,6 +1031,23 @@ xfs_reflink_remap_extent(
>  
>  	trace_xfs_reflink_remap_extent_dest(ip, &smap);
>  
> +	/*
> +	 * Two extents mapped to the same physical block must not have
> +	 * different states; that's filesystem corruption.  Move on to the next
> +	 * extent if they're both holes or both the same physical extent.
> +	 */
> +	if (dmap->br_startblock == smap.br_startblock) {
> +		ASSERT(dmap->br_startblock == smap.br_startblock);

That assert duplicates the logic in the if statement. Was this intended
to be the length check I asked for? If so it looks like that was added
previously so perhaps this can just drop off. With that fixed up:

Reviewed-by: Brian Foster <bfoster@redhat.com>

> +		if (dmap->br_state != smap.br_state)
> +			error = -EFSCORRUPTED;
> +		goto out_cancel;
> +	}
> +
> +	/* If both extents are unwritten, leave them alone. */
> +	if (dmap->br_state == XFS_EXT_UNWRITTEN &&
> +	    smap.br_state == XFS_EXT_UNWRITTEN)
> +		goto out_cancel;
> +
>  	/* No reflinking if the AG of the dest mapping is low on space. */
>  	if (dmap_written) {
>  		error = xfs_reflink_ag_has_free_space(mp,
> 


  reply	other threads:[~2020-06-25 12:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25  1:17 [PATCH v2 0/9] xfs: reflink cleanups Darrick J. Wong
2020-06-25  1:17 ` [PATCH 1/9] xfs: fix reflink quota reservation accounting error Darrick J. Wong
2020-06-25 12:26   ` Brian Foster
2020-07-01  8:07   ` Christoph Hellwig
2020-06-25  1:17 ` [PATCH 2/9] xfs: rename xfs_bmap_is_real_extent to is_written_extent Darrick J. Wong
2020-06-25 12:26   ` Brian Foster
2020-07-01  8:08   ` Christoph Hellwig
2020-06-25  1:17 ` [PATCH 3/9] xfs: redesign the reflink remap loop to fix blkres depletion crash Darrick J. Wong
2020-06-25 12:27   ` Brian Foster
2020-06-25 16:57     ` Darrick J. Wong
2020-06-25 17:23   ` [PATCH v4.2 " Darrick J. Wong
2020-06-26 11:57     ` Brian Foster
2020-06-26 16:40       ` Darrick J. Wong
2020-07-01  8:20     ` Christoph Hellwig
2020-06-25  1:18 ` [PATCH 4/9] xfs: only reserve quota blocks for bmbt changes if we're changing the data fork Darrick J. Wong
2020-06-25 12:27   ` Brian Foster
2020-07-01  8:21   ` Christoph Hellwig
2020-06-25  1:18 ` [PATCH 5/9] xfs: only reserve quota blocks if we're mapping into a hole Darrick J. Wong
2020-06-25 12:28   ` Brian Foster
2020-07-01  8:22   ` Christoph Hellwig
2020-06-25  1:18 ` [PATCH 6/9] xfs: reflink can skip remap existing mappings Darrick J. Wong
2020-06-25 12:28   ` Brian Foster [this message]
2020-06-25 16:49     ` Darrick J. Wong
2020-06-25  1:18 ` [PATCH 7/9] xfs: fix xfs_reflink_remap_prep calling conventions Darrick J. Wong
2020-07-01  8:23   ` Christoph Hellwig
2020-06-25  1:18 ` [PATCH 8/9] xfs: refactor locking and unlocking two inodes against userspace IO Darrick J. Wong
2020-07-01  8:26   ` Christoph Hellwig
2020-06-25  1:18 ` [PATCH 9/9] xfs: move helpers that lock and unlock " Darrick J. Wong
2020-07-01  8:27   ` Christoph Hellwig
2020-06-28 12:06 ` [PATCH v2 0/9] xfs: reflink cleanups Edwin Török
2020-06-28 22:36   ` Darrick J. Wong

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=20200625122818.GH2863@bfoster \
    --to=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=edwin@etorok.net \
    --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