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@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/4] xfs: check owner of dir3 blocks
Date: Thu, 5 Mar 2020 09:48:48 -0800	[thread overview]
Message-ID: <20200305174848.GT8045@magnolia> (raw)
In-Reply-To: <20200305165128.GE7630@infradead.org>

On Thu, Mar 05, 2020 at 08:51:28AM -0800, Christoph Hellwig wrote:
> On Fri, Feb 28, 2020 at 05:49:01PM -0800, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> > 
> > Check the owner field of dir3 block headers.
> > 
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> 
> Looks good,
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> 
> > +		xfs_verifier_error(*bpp, -EFSCORRUPTED, fa);
> > +		(*bpp)->b_flags &= ~XBF_DONE;
> > +		xfs_trans_brelse(tp, *bpp);
> > +		*bpp = NULL;
> > +		return -EFSCORRUPTED;
> 
> Although I wonder if we should factor this repeated sniplet into a
> helper..

Yes.  Dave and I were discussing in patch 1 that
xfs_buf_corruption_error() is the correct function to call for a buffer
that we've decided is corrupt outside of a read verifier, so this all
becomes:

if (fa) {
	xfs_buf_corruption_error(*bpp...);
	xfs_trans_brelse(tp, *bpp);
	*bpp = NULL;
	return -EFSCORRUPTED;
}

(We also observed that xfs_buf_corruption_error ought to stale the
corrupt buffer to get it out of the system asap.)

--D

      reply	other threads:[~2020-03-05 17:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-29  1:48 [PATCH 0/4] xfs: fix errors in directory verifiers Darrick J. Wong
2020-02-29  1:48 ` [PATCH 1/4] xfs: fix buffer state when we reject a corrupt dir free block Darrick J. Wong
2020-03-02 18:11   ` Allison Collins
2020-03-02 23:54   ` Eric Sandeen
2020-03-03 16:38     ` Darrick J. Wong
2020-03-03 17:43       ` Darrick J. Wong
2020-03-03 23:45       ` Dave Chinner
2020-03-05 17:45         ` Darrick J. Wong
2020-03-03 20:19   ` Darrick J. Wong
2020-03-05 16:49   ` Christoph Hellwig
2020-02-29  1:48 ` [PATCH 2/4] xfs: check owner of dir3 free blocks Darrick J. Wong
2020-03-02 18:11   ` Allison Collins
2020-03-03  0:04   ` Eric Sandeen
2020-03-03 16:08     ` Darrick J. Wong
2020-03-03 16:10       ` Eric Sandeen
2020-03-05 16:50   ` Christoph Hellwig
2020-02-29  1:48 ` [PATCH 3/4] xfs: check owner of dir3 data blocks Darrick J. Wong
2020-03-02 18:12   ` Allison Collins
2020-03-03 16:43     ` Darrick J. Wong
2020-03-05 16:50   ` Christoph Hellwig
2020-02-29  1:49 ` [PATCH 4/4] xfs: check owner of dir3 blocks Darrick J. Wong
2020-03-02 18:12   ` Allison Collins
2020-03-05 16:51   ` Christoph Hellwig
2020-03-05 17:48     ` Darrick J. Wong [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=20200305174848.GT8045@magnolia \
    --to=darrick.wong@oracle.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