linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>, Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH v3] xfs: avoid mount-time deadlock in CoW extent recovery
Date: Fri, 19 May 2017 07:31:38 -0400	[thread overview]
Message-ID: <20170519113138.GC64091@bfoster.bfoster> (raw)
In-Reply-To: <20170518220249.GI4514@birch.djwong.org>

On Thu, May 18, 2017 at 03:02:49PM -0700, Darrick J. Wong wrote:
> If a malicious user corrupts the refcount btree to cause a cycle between
> different levels of the tree, the next mount attempt will deadlock in
> the CoW recovery routine while grabbing buffer locks.  We can use the
> ability to re-grab a buffer that was previous locked to a transaction to
> avoid deadlocks, so do that here.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> v3: fix the error exit paths always to free the list
> v2: leave a comment discussing why we use an empty transaction
> ---

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

>  fs/xfs/libxfs/xfs_refcount.c |   43 ++++++++++++++++++++++++++++++------------
>  1 file changed, 31 insertions(+), 12 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_refcount.c b/fs/xfs/libxfs/xfs_refcount.c
> index b177ef3..82a38d8 100644
> --- a/fs/xfs/libxfs/xfs_refcount.c
> +++ b/fs/xfs/libxfs/xfs_refcount.c
> @@ -1629,13 +1629,28 @@ xfs_refcount_recover_cow_leftovers(
>  	if (mp->m_sb.sb_agblocks >= XFS_REFC_COW_START)
>  		return -EOPNOTSUPP;
>  
> -	error = xfs_alloc_read_agf(mp, NULL, agno, 0, &agbp);
> +	INIT_LIST_HEAD(&debris);
> +
> +	/*
> +	 * In this first part, we use an empty transaction to gather up
> +	 * all the leftover CoW extents so that we can subsequently
> +	 * delete them.  The empty transaction is used to avoid
> +	 * a buffer lock deadlock if there happens to be a loop in the
> +	 * refcountbt because we're allowed to re-grab a buffer that is
> +	 * already attached to our transaction.  When we're done
> +	 * recording the CoW debris we cancel the (empty) transaction
> +	 * and everything goes away cleanly.
> +	 */
> +	error = xfs_trans_alloc_empty(mp, &tp);
>  	if (error)
>  		return error;
> -	cur = xfs_refcountbt_init_cursor(mp, NULL, agbp, agno, NULL);
> +
> +	error = xfs_alloc_read_agf(mp, tp, agno, 0, &agbp);
> +	if (error)
> +		goto out_trans;
> +	cur = xfs_refcountbt_init_cursor(mp, tp, agbp, agno, NULL);
>  
>  	/* Find all the leftover CoW staging extents. */
> -	INIT_LIST_HEAD(&debris);
>  	memset(&low, 0, sizeof(low));
>  	memset(&high, 0, sizeof(high));
>  	low.rc.rc_startblock = XFS_REFC_COW_START;
> @@ -1645,10 +1660,11 @@ xfs_refcount_recover_cow_leftovers(
>  	if (error)
>  		goto out_cursor;
>  	xfs_btree_del_cursor(cur, XFS_BTREE_NOERROR);
> -	xfs_buf_relse(agbp);
> +	xfs_trans_brelse(tp, agbp);
> +	xfs_trans_cancel(tp);
>  
>  	/* Now iterate the list to free the leftovers */
> -	list_for_each_entry(rr, &debris, rr_list) {
> +	list_for_each_entry_safe(rr, n, &debris, rr_list) {
>  		/* Set up transaction. */
>  		error = xfs_trans_alloc(mp, &M_RES(mp)->tr_write, 0, 0, 0, &tp);
>  		if (error)
> @@ -1676,8 +1692,16 @@ xfs_refcount_recover_cow_leftovers(
>  		error = xfs_trans_commit(tp);
>  		if (error)
>  			goto out_free;
> +
> +		list_del(&rr->rr_list);
> +		kmem_free(rr);
>  	}
>  
> +	return error;
> +out_defer:
> +	xfs_defer_cancel(&dfops);
> +out_trans:
> +	xfs_trans_cancel(tp);
>  out_free:
>  	/* Free the leftover list */
>  	list_for_each_entry_safe(rr, n, &debris, rr_list) {
> @@ -1688,11 +1712,6 @@ xfs_refcount_recover_cow_leftovers(
>  
>  out_cursor:
>  	xfs_btree_del_cursor(cur, XFS_BTREE_ERROR);
> -	xfs_buf_relse(agbp);
> -	goto out_free;
> -
> -out_defer:
> -	xfs_defer_cancel(&dfops);
> -	xfs_trans_cancel(tp);
> -	goto out_free;
> +	xfs_trans_brelse(tp, agbp);
> +	goto out_trans;
>  }
> 
> ----- End forwarded message -----
> --
> 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-05-19 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 22:02 [PATCH v3] xfs: avoid mount-time deadlock in CoW extent recovery Darrick J. Wong
2017-05-19 11:31 ` Brian Foster [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=20170519113138.GC64091@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --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;
as well as URLs for NNTP newsgroup(s).