From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/3] xfs: clean up the metadata validation in xfs_swap_extent_rmap
Date: Wed, 6 May 2020 09:45:15 -0700 [thread overview]
Message-ID: <20200506164515.GU5703@magnolia> (raw)
In-Reply-To: <20200506145633.GB7864@infradead.org>
On Wed, May 06, 2020 at 07:56:33AM -0700, Christoph Hellwig wrote:
> On Mon, May 04, 2020 at 06:10:22PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Bail out if there's something not right with either file's fork
> > mappings.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> > fs/xfs/xfs_bmap_util.c | 31 +++++++++++++++++++++++--------
> > 1 file changed, 23 insertions(+), 8 deletions(-)
> >
> >
> > diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c
> > index cc23a3e23e2d..2774939e176d 100644
> > --- a/fs/xfs/xfs_bmap_util.c
> > +++ b/fs/xfs/xfs_bmap_util.c
> > @@ -1342,8 +1342,16 @@ xfs_swap_extent_rmap(
> > &nimaps, 0);
> > if (error)
> > goto out;
> > - ASSERT(nimaps == 1);
> > - ASSERT(tirec.br_startblock != DELAYSTARTBLOCK);
> > + if (nimaps != 1 || tirec.br_startblock == DELAYSTARTBLOCK) {
> > + /*
> > + * We should never get no mapping or a delalloc extent
> > + * since the donor file should have been flushed by the
> > + * caller.
> > + */
> > + ASSERT(0);
> > + error = -EINVAL;
> > + goto out;
> > + }
>
> I'm not even sure the !nimaps case still exists. Usually this will
> return a hole extent, which we don't seem to handle here?
xfs_bmap_unmap_extent and xfs_bmap_map_extent are NOPs if you pass
them a hole.
But yeah, the !nimaps case doesn't seem to exist anymore.
> In general I think this code would be improved quite a bit by using
> xfs_iext_lookup_extent instead of xfs_bmapi_read.
>
> Same for the second hunk.
I'd rather not make major changes to this code because my long range
plan is to replace all this with a much cleaner implementation in the
atomic file update series[1]. This patchset bandages the wtfs that I
found while writing that series, projecting that review of atomic file
updates is going to take a while...
--D
[1] https://lwn.net/ml/linux-fsdevel/158812825316.168506.932540609191384366.stgit@magnolia/
next prev parent reply other threads:[~2020-05-06 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 1:10 [PATCH 0/3] xfs: random SWAPEXT fixes Darrick J. Wong
2020-05-05 1:10 ` [PATCH 1/3] xfs: clean up the error handling in xfs_swap_extents Darrick J. Wong
2020-05-06 14:46 ` Christoph Hellwig
2020-05-05 1:10 ` [PATCH 2/3] xfs: clean up the metadata validation in xfs_swap_extent_rmap Darrick J. Wong
2020-05-06 14:56 ` Christoph Hellwig
2020-05-06 16:45 ` Darrick J. Wong [this message]
2020-05-05 1:10 ` [PATCH 3/3] xfs: actually account for quota changes in xfs_swap_extents Darrick J. Wong
2020-05-06 14:57 ` Christoph Hellwig
2020-05-06 16:34 ` Darrick J. Wong
2020-05-07 6:02 ` Christoph Hellwig
2020-05-12 23:42 ` 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=20200506164515.GU5703@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