public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 8/9] xfs_mdrestore: EXTERNALLOG is a compat value, not incompat
Date: Mon, 27 Nov 2023 10:27:38 -0800	[thread overview]
Message-ID: <20231127182738.GD2766956@frogsfrogsfrogs> (raw)
In-Reply-To: <ZV70YNvPWauYckC4@infradead.org>

On Wed, Nov 22, 2023 at 10:42:40PM -0800, Christoph Hellwig wrote:
> On Wed, Nov 22, 2023 at 03:07:33PM -0800, Darrick J. Wong wrote:
> > @@ -280,10 +278,8 @@ read_header_v2(
> >  	if (h->v2.xmh_reserved != 0)
> >  		fatal("Metadump header's reserved field has a non-zero value\n");
> >  
> > -	want_external_log = !!(be32_to_cpu(h->v2.xmh_incompat_flags) &
> > -			XFS_MD2_COMPAT_EXTERNALLOG);
> > -
> > -	if (want_external_log && !mdrestore.external_log)
> > +	if ((h->v2.xmh_compat_flags & cpu_to_be32(XFS_MD2_COMPAT_EXTERNALLOG)) &&
> > +	    !mdrestore.external_log)
> 
> Nit: overly long line.  Trivially fixable by just inverting the
> conditions :)

Hmm.  Or I could decode the ondisk field into a stack variable so that
future flags don't have to deal with that:

	compat = be32_to_cpu(h->v2.xmh_compat_flags);

	if (!mdrestore.external_log && (compat & XFS_MD2_COMPAT_EXTERNALLOG))
		fatal("External Log device is required\n");


--D

> 
> Otherwise looks good:
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> 

  parent reply	other threads:[~2023-11-27 18:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 23:06 [PATCHSET 0/9] xfsprogs: minor fixes for 6.6 Darrick J. Wong
2023-11-22 23:06 ` [PATCH 1/9] libfrog: move 64-bit division wrappers to libfrog Darrick J. Wong
2023-11-23  6:34   ` Christoph Hellwig
2023-11-24  9:09   ` Chandan Babu R
2023-11-22 23:06 ` [PATCH 2/9] libxfs: don't UAF a requeued EFI Darrick J. Wong
2023-11-23  6:36   ` Christoph Hellwig
2023-11-27 18:10     ` Darrick J. Wong
2023-11-28  5:37       ` Christoph Hellwig
2023-11-28 17:01         ` Darrick J. Wong
2023-11-28 17:09           ` Christoph Hellwig
2023-11-24  9:10   ` Chandan Babu R
2023-11-22 23:07 ` [PATCH 3/9] xfs_copy: actually do directio writes to block devices Darrick J. Wong
2023-11-23  6:40   ` Christoph Hellwig
2023-11-27 18:14     ` Darrick J. Wong
2023-11-22 23:07 ` [PATCH 4/9] xfs_db: report the device associated with each io cursor Darrick J. Wong
2023-11-23  6:41   ` Christoph Hellwig
2023-11-27 18:24     ` Darrick J. Wong
2023-11-28  5:37       ` Christoph Hellwig
2023-11-22 23:07 ` [PATCH 5/9] xfs_metadump.8: update for external log device options Darrick J. Wong
2023-11-23  6:41   ` Christoph Hellwig
2023-11-24  9:11   ` Chandan Babu R
2023-11-22 23:07 ` [PATCH 6/9] xfs_mdrestore: fix uninitialized variables in mdrestore main Darrick J. Wong
2023-11-23  6:41   ` Christoph Hellwig
2023-11-24  9:11   ` Chandan Babu R
2023-11-22 23:07 ` [PATCH 7/9] xfs_mdrestore: emit newlines for fatal errors Darrick J. Wong
2023-11-23  6:41   ` Christoph Hellwig
2023-11-24  9:12   ` Chandan Babu R
2023-11-22 23:07 ` [PATCH 8/9] xfs_mdrestore: EXTERNALLOG is a compat value, not incompat Darrick J. Wong
2023-11-23  6:42   ` Christoph Hellwig
2023-11-23  6:42     ` Christoph Hellwig
2023-11-27 18:27     ` Darrick J. Wong [this message]
2023-11-28  5:38       ` Christoph Hellwig
2023-11-24  9:14   ` Chandan Babu R
2023-11-22 23:07 ` [PATCH 9/9] xfs_mdrestore: fix missed progress reporting Darrick J. Wong
2023-11-23  6:44   ` Christoph Hellwig
2023-11-24  9:14   ` Chandan Babu R

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=20231127182738.GD2766956@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --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