From: "Darrick J. Wong" <djwong@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: Dave Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 2/9] xfs/070: filter new superblock verifier messages
Date: Wed, 29 Jun 2022 15:41:10 -0700 [thread overview]
Message-ID: <YrzVBs9h0lzYFvCo@magnolia> (raw)
In-Reply-To: <20220629091248.vtqtlk2wvqkmtxkm@zlang-mailbox>
On Wed, Jun 29, 2022 at 05:12:48PM +0800, Zorro Lang wrote:
> On Wed, Jun 29, 2022 at 02:15:47PM +1000, Dave Chinner wrote:
> > On Tue, Jun 28, 2022 at 01:21:28PM -0700, Darrick J. Wong wrote:
> > > From: Darrick J. Wong <djwong@kernel.org>
> > >
> > > In Linux 5.19, the superblock verifier logging changed to elaborate on
> > > what was wrong. Fix the xfs_repair filtering function to accomodate
> > > this development.
> > >
> > > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > > ---
> > > common/repair | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > >
> > > diff --git a/common/repair b/common/repair
> > > index 463ef9db..398e9904 100644
> > > --- a/common/repair
> > > +++ b/common/repair
> > > @@ -29,6 +29,7 @@ _filter_repair()
> > > # for sb
> > > /- agno = / && next; # remove each AG line (variable number)
> > > s/(pointer to) (\d+)/\1 INO/;
> > > +s/Superblock has bad magic number.*/bad magic number/;
> > > # Changed inode output in 5.5.0
> > > s/sb root inode value /sb root inode /;
> > > s/realtime bitmap inode value /realtime bitmap inode /;
> >
> > Didn't I already fix that in commit 4c76d0ba ("xfs/070: filter the
> > bad sb magic number error")?
Ah whoops I guess we can drop this one then.
> Yes, you've added a line as below:
> s/^Superblock has (bad magic number) 0x.*/\1/;
> which is equal to:
> s/Superblock has bad magic number.*/bad magic number/;
> So we need to fix it again.
We .... do?
--D
>
> >
> > Cheers,
> >
> > Dave.
> >
> > --
> > Dave Chinner
> > david@fromorbit.com
> >
>
next prev parent reply other threads:[~2022-06-29 22:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 20:21 [PATCHSET 0/9] fstests: random fixes Darrick J. Wong
2022-06-28 20:21 ` [PATCH 1/9] seek_sanity_test: fix allocation unit detection on XFS realtime Darrick J. Wong
2022-06-29 7:41 ` Christoph Hellwig
2022-07-28 1:37 ` liuyd.fnst
2022-07-28 2:31 ` Darrick J. Wong
2022-07-28 2:37 ` Darrick J. Wong
2022-07-28 3:38 ` liuyd.fnst
2022-07-28 3:54 ` Darrick J. Wong
2022-06-28 20:21 ` [PATCH 2/9] xfs/070: filter new superblock verifier messages Darrick J. Wong
2022-06-29 4:15 ` Dave Chinner
2022-06-29 9:12 ` Zorro Lang
2022-06-29 22:41 ` Darrick J. Wong [this message]
2022-06-30 2:18 ` Zorro Lang
2022-06-28 20:21 ` [PATCH 3/9] xfs: test mkfs.xfs sizing of internal logs that Darrick J. Wong
2022-06-29 4:18 ` Dave Chinner
2022-06-29 22:43 ` Darrick J. Wong
2022-06-30 6:37 ` Zorro Lang
2022-06-30 19:32 ` Darrick J. Wong
2022-06-28 20:21 ` [PATCH 4/9] xfs: test xfs_copy doesn't do cached read before libxfs_mount Darrick J. Wong
2022-06-29 4:20 ` Dave Chinner
2022-06-29 22:46 ` Darrick J. Wong
2022-06-30 0:48 ` [PATCH v2.1 " Darrick J. Wong
2022-07-01 1:06 ` Dave Chinner
2022-06-28 20:21 ` [PATCH 5/9] check: document mkfs.xfs reliance on fstests exports Darrick J. Wong
2022-06-29 4:22 ` Dave Chinner
2022-06-28 20:21 ` [PATCH 6/9] xfs/109: handle larger minimum filesystem size Darrick J. Wong
2022-06-29 4:22 ` Dave Chinner
2022-06-28 20:21 ` [PATCH 7/9] xfs/018: fix LARP testing for small block sizes Darrick J. Wong
2022-06-28 20:22 ` [PATCH 8/9] xfs/166: fix golden output failures when multipage folios enabled Darrick J. Wong
2022-06-29 4:23 ` Dave Chinner
2022-06-28 20:22 ` [PATCH 9/9] xfs/547: fix problems with realtime Darrick J. Wong
2022-07-05 14:28 ` [PATCHSET 0/9] fstests: random fixes Zorro Lang
2022-07-05 22:04 ` 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=YrzVBs9h0lzYFvCo@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@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