From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: hch@lst.de, cem@kernel.org, stable@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/6] xfs: rtsummary scrub should treat rtbitmap corruption errors as an xref error
Date: Thu, 16 Jul 2026 10:19:16 +0200 [thread overview]
Message-ID: <20260716081916.GE12330@lst.de> (raw)
In-Reply-To: <178416797424.2008054.49983972584839221.stgit@frogsfrogsfrogs>
On Wed, Jul 15, 2026 at 11:06:53PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> LOLLM notes the discrepancy between the comment saying that this is an
> xref error and the code, which marks a (non-xref) corruption error.
> This appears to be a regression.
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-07-16 8:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 6:06 [PATCHSET] xfs: LLM-inspired bug fixes, part 3 Darrick J. Wong
2026-07-16 6:06 ` [PATCH 1/6] xfs: check cowextsize in xrep_inode_cowextsize Darrick J. Wong
2026-07-16 8:18 ` Christoph Hellwig
2026-07-16 6:06 ` [PATCH 2/6] xfs: fix transaction block reservation in xrep_rtbitmap Darrick J. Wong
2026-07-16 8:18 ` Christoph Hellwig
2026-07-16 6:06 ` [PATCH 3/6] xfs: rtsummary scrub should treat rtbitmap corruption errors as an xref error Darrick J. Wong
2026-07-16 8:19 ` Christoph Hellwig [this message]
2026-07-16 6:07 ` [PATCH 4/6] xfs: zero i_nlink before repair puts inode on unlinked list Darrick J. Wong
2026-07-16 8:19 ` Christoph Hellwig
2026-07-16 6:07 ` [PATCH 5/6] xfs: mark nonzero sb_gquotino as corrupt on metadir filesystems Darrick J. Wong
2026-07-16 8:19 ` Christoph Hellwig
2026-07-16 6:07 ` [PATCH 6/6] xfs: don't livelock in scrub on a circular unlinked list Darrick J. Wong
2026-07-16 8:24 ` Christoph Hellwig
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=20260716081916.GE12330@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@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