public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: bodonnel@redhat.com, linux-xfs@vger.kernel.org, djwong@kernel.org
Subject: Re: [PATCH] xfs_repair: handling a block with bad crc, bad uuid, and bad magic number needs fixing
Date: Fri, 21 Mar 2025 00:32:56 -0700	[thread overview]
Message-ID: <Z90WKKkLtqFvMNkK@infradead.org> (raw)
In-Reply-To: <81461ddc-bc91-4bbe-9828-956a67488856@sandeen.net>

On Thu, Mar 20, 2025 at 05:21:22PM -0500, Eric Sandeen wrote:
> For anyone interested in evaluating this problem, here is a cleanroom'd
> reproducer metadump image that demonstrates it.

Which makes me wonder again if we want these kinds of images stored
in xfstests somehow (or figure out a way to create them by fuzzing)


  reply	other threads:[~2025-03-21  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20 20:25 [PATCH] xfs_repair: handling a block with bad crc, bad uuid, and bad magic number needs fixing bodonnel
2025-03-20 22:21 ` Eric Sandeen
2025-03-21  7:32   ` Christoph Hellwig [this message]
2025-03-20 23:28 ` Eric Sandeen
2025-03-21  7:35   ` 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=Z90WKKkLtqFvMNkK@infradead.org \
    --to=hch@infradead.org \
    --cc=bodonnel@redhat.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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