From: Gao Xiang <hsiangkao@redhat.com>
To: Brian Foster <bfoster@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 22:11:41 +0800 [thread overview]
Message-ID: <20201013141141.GC12025@xiangao.remote.csb> (raw)
In-Reply-To: <20201013140726.GH966478@bfoster>
On Tue, Oct 13, 2020 at 10:07:26AM -0400, Brian Foster wrote:
> 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.
Agree, that expression looks better <nod>
I will switch to it then. Thanks!
Thanks,
Gao Xiang
>
> Brian
prev parent reply other threads:[~2020-10-13 14:11 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
2020-10-13 14:11 ` Gao Xiang [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=20201013141141.GC12025@xiangao.remote.csb \
--to=hsiangkao@redhat.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox