All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Gao Xiang <hsiangkao@redhat.com>
Cc: linux-xfs@vger.kernel.org,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	Eric Sandeen <sandeen@redhat.com>,
	Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH v2] xfs: introduce xfs_validate_stripe_geometry()
Date: Tue, 13 Oct 2020 10:07:26 -0400	[thread overview]
Message-ID: <20201013140726.GH966478@bfoster> (raw)
In-Reply-To: <20201013135537.GB12025@xiangao.remote.csb>

On Tue, Oct 13, 2020 at 09:55:37PM +0800, Gao Xiang wrote:
> Hi Brian,
> 
> On Tue, Oct 13, 2020 at 09:44:11AM -0400, Brian Foster wrote:
> > On Tue, Oct 13, 2020 at 11:48:53AM +0800, Gao Xiang wrote:
> > > Introduce a common helper to consolidate stripe validation process.
> > > Also make kernel code xfs_validate_sb_common() use it first.
> > > 
> > > Signed-off-by: Gao Xiang <hsiangkao@redhat.com>
> > > ---
> > > v1: https://lore.kernel.org/r/20201009050546.32174-1-hsiangkao@redhat.com
> > > 
> > > changes since v1:
> > >  - rename the helper to xfs_validate_stripe_geometry() (Brian);
> > >  - drop a new added trailing newline in xfs_sb.c (Brian);
> > >  - add a "bool silent" argument to avoid too many error messages (Brian).
> > > 
> > >  fs/xfs/libxfs/xfs_sb.c | 70 +++++++++++++++++++++++++++++++++++-------
> > >  fs/xfs/libxfs/xfs_sb.h |  3 ++
> > >  2 files changed, 62 insertions(+), 11 deletions(-)
> > > 
> > > diff --git a/fs/xfs/libxfs/xfs_sb.c b/fs/xfs/libxfs/xfs_sb.c
> > > index 5aeafa59ed27..9178715ded45 100644
> > > --- a/fs/xfs/libxfs/xfs_sb.c
> > > +++ b/fs/xfs/libxfs/xfs_sb.c
> > > @@ -360,21 +360,18 @@ xfs_validate_sb_common(
> > >  		}
> > >  	}
> > >  
> > > -	if (sbp->sb_unit) {
> > > -		if (!xfs_sb_version_hasdalign(sbp) ||
> > > -		    sbp->sb_unit > sbp->sb_width ||
> > > -		    (sbp->sb_width % sbp->sb_unit) != 0) {
> > > -			xfs_notice(mp, "SB stripe unit sanity check failed");
> > > -			return -EFSCORRUPTED;
> > > -		}
> > > -	} else if (xfs_sb_version_hasdalign(sbp)) {
> > > +	/*
> > > +	 * Either (sb_unit and !hasdalign) or (!sb_unit and hasdalign)
> > > +	 * would imply the image is corrupted.
> > > +	 */
> > > +	if (!sbp->sb_unit ^ !xfs_sb_version_hasdalign(sbp)) {
> > 
> > This can be simplified to drop the negations (!), right?
> 
> Thanks for the suggestion.
> 
> yet nope, honestly I don't think so, the reason is that sbp->sb_unit is
> an integer here rather than a boolean, so negations cannot be
> simplified and I think it's simpliest now... (some boolean algebra...)
> 

Oh, right. So you'd actually need something like (!!sunit ^ hasdalign())
to avoid the bit operation.

Brian

> > 
> > >  		xfs_notice(mp, "SB stripe alignment sanity check failed");
> 
> ...
> 
> > > +	if (sectorsize && sunit % sectorsize) {
> > > +		if (!silent)
> > > +			xfs_notice(mp,
> > > +"stripe unit (%lld) must be a multiple of the sector size (%d)",
> > > +				   sunit, sectorsize);
> > > +		return false;
> > > +	}
> > > +
> > > +	if (sunit && !swidth) {
> > > +		if (!silent)
> > > +			xfs_notice(mp,
> > > +"invalid stripe unit (%lld) and stripe width of 0", sunit);
> > > +		return false;
> > > +	}
> > > +
> > > +	if (!sunit && swidth) {
> > > +		if (!silent)
> > > +			xfs_notice(mp,
> > > +"invalid stripe width (%lld) and stripe unit of 0", swidth);
> > > +		return false;
> > > +	}
> > > +
> > > +	if (sunit > swidth) {
> > > +		if (!silent)
> > > +			xfs_notice(mp,
> > > +"stripe unit (%lld) is larger than the stripe width (%lld)", sunit, swidth);
> > > +		return false;
> > > +	}
> > > +
> > > +	if (sunit && (swidth % sunit)) {
> > 
> > It might be good to use (or not) params consistently. I.e., the
> > sectorsize check earlier in the function has similar logic structure but
> > drops the params.
> 
> Yeah, that is due to the line was copied from somewhere else... so...
> Anyway, I can resend a quick fix for this if needed. Wait a sec
> for some potential feedback...
> 
> Thanks,
> Gao Xiang
> 
> > 
> > Those nits aside:
> > 
> > Reviewed-by: Brian Foster <bfoster@redhat.com>
> > 
> 


  reply	other threads:[~2020-10-13 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13  3:48 [PATCH v2] xfs: introduce xfs_validate_stripe_geometry() Gao Xiang
2020-10-13 13:44 ` Brian Foster
2020-10-13 13:55   ` Gao Xiang
2020-10-13 14:07     ` Brian Foster [this message]
2020-10-13 14:11       ` Gao Xiang

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=20201013140726.GH966478@bfoster \
    --to=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hsiangkao@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.