linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: david@fromorbit.com, linux-xfs@vger.kernel.org,
	Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH v2 1/7] xfs: rework refcount cow recovery error handling
Date: Mon, 10 Oct 2016 11:21:52 -0700	[thread overview]
Message-ID: <20161010182152.GC22379@birch.djwong.org> (raw)
In-Reply-To: <20161010102113.GC18359@infradead.org>

On Mon, Oct 10, 2016 at 03:21:13AM -0700, Christoph Hellwig wrote:
> On Sun, Oct 09, 2016 at 11:11:22PM -0700, Darrick J. Wong wrote:
> > The error handling in xfs_refcount_recover_cow_leftovers is confused
> > and can potentially leak memory, so rework it to release resources
> > correctly on error.
> > 
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > Reported-by: Brian Foster <bfoster@redhat.com>
> > ---
> >  fs/xfs/libxfs/xfs_refcount.c |   16 ++++++----------
> >  1 file changed, 6 insertions(+), 10 deletions(-)
> > 
> > diff --git a/fs/xfs/libxfs/xfs_refcount.c b/fs/xfs/libxfs/xfs_refcount.c
> > index 56bfef1..955b1d9 100644
> > --- a/fs/xfs/libxfs/xfs_refcount.c
> > +++ b/fs/xfs/libxfs/xfs_refcount.c
> > @@ -1643,7 +1643,7 @@ xfs_refcount_recover_cow_leftovers(
> >  	error = xfs_btree_query_range(cur, &low, &high,
> >  			xfs_refcount_recover_extent, &debris);
> >  	if (error)
> > -		goto out_error;
> > +		goto out_cursor;
> >  	xfs_btree_del_cursor(cur, XFS_BTREE_NOERROR);
> >  	xfs_buf_relse(agbp);
> >  
> > @@ -1675,26 +1675,22 @@ xfs_refcount_recover_cow_leftovers(
> >  
> >  		error = xfs_trans_commit(tp);
> >  		if (error)
> > +			goto out_free;
> >  	}
> >  	goto out_free;
> 
> don't we need to also delete the cursor after a successful exit?

Gah.  Yeah.  Serves me right for trying to code patches on Sunday night.

I think Dave already made a separate fix, though, so I'll wait for the
next for-next update and see what needs to be fixed.

--D

  reply	other threads:[~2016-10-10 18:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 23:07 [PATCH 0/7] xfs: reflink fixes Darrick J. Wong
2016-10-07 23:07 ` [PATCH 1/7] xfs: rework refcount cow recovery error handling Darrick J. Wong
2016-10-10  5:37   ` Dave Chinner
2016-10-10  6:10     ` Darrick J. Wong
2016-10-10  6:11   ` [PATCH v2 " Darrick J. Wong
2016-10-10 10:21     ` Christoph Hellwig
2016-10-10 18:21       ` Darrick J. Wong [this message]
2016-10-10 20:25         ` Dave Chinner
2016-10-10 21:46           ` Darrick J. Wong
2016-10-07 23:07 ` [PATCH 2/7] xfs: check inode reflink flag before calling reflink functions Darrick J. Wong
2016-10-10  5:24   ` Dave Chinner
2016-10-10 10:18   ` Christoph Hellwig
2016-10-07 23:07 ` [PATCH 3/7] xfs: reduce stack usage of _reflink_clear_inode_flag Darrick J. Wong
2016-10-10  5:25   ` Dave Chinner
2016-10-10 10:17   ` Christoph Hellwig
2016-10-07 23:07 ` [PATCH 4/7] xfs: remove isize check from unshare operation Darrick J. Wong
2016-10-10  5:26   ` Dave Chinner
2016-10-10 10:21   ` Christoph Hellwig
2016-10-07 23:07 ` [PATCH 5/7] xfs: fix label inaccuracies Darrick J. Wong
2016-10-10  5:27   ` Dave Chinner
2016-10-10 10:22   ` Christoph Hellwig
2016-10-07 23:07 ` [PATCH 6/7] xfs: fix error initialization Darrick J. Wong
2016-10-08 15:55   ` Eric Sandeen
2016-10-10  5:36     ` Dave Chinner
2016-10-10 10:23     ` Christoph Hellwig
2016-10-07 23:08 ` [PATCH 7/7] xfs: clear reflink flag if setting realtime flag Darrick J. Wong
2016-10-10  5:29   ` Dave Chinner
2016-10-10 10:24   ` Christoph Hellwig
2016-10-10 12:25     ` Dave Chinner
2016-10-10 12:45       ` Christoph Hellwig
2016-10-10 12:59         ` Dave Chinner
2016-10-10 17:18         ` Darrick J. Wong
2016-10-10 12:44   ` Brian Foster
2016-10-10 18:10     ` 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=20161010182152.GC22379@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=bfoster@redhat.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --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).