From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Andrey Albershteyn <aalbersh@kernel.org>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs_io: use the XFS_ERRTAG macro to generate injection targets
Date: Mon, 15 Sep 2025 22:51:13 +0200 [thread overview]
Message-ID: <20250915205113.GC5650@lst.de> (raw)
In-Reply-To: <20250915191115.GZ8096@frogsfrogsfrogs>
On Mon, Sep 15, 2025 at 12:11:15PM -0700, Darrick J. Wong wrote:
> On Mon, Sep 15, 2025 at 06:33:17AM -0700, Christoph Hellwig wrote:
> > Use the new magic macro table provided by libxfs to autogenerate
> > the list of valid error injection targets.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> With this applied we no longer have to manually update inject.c every
> time we do a libxfs port too, right?
Exactly.
prev parent reply other threads:[~2025-09-15 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 13:33 xfsprogs: cleanup error injection Christoph Hellwig
2025-09-15 13:33 ` [PATCH 1/2] xfs: centralize error tag definitions Christoph Hellwig
2025-09-15 13:33 ` [PATCH 2/2] xfs_io: use the XFS_ERRTAG macro to generate injection targets Christoph Hellwig
2025-09-15 19:11 ` Darrick J. Wong
2025-09-15 20:51 ` Christoph Hellwig [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=20250915205113.GC5650@lst.de \
--to=hch@lst.de \
--cc=aalbersh@kernel.org \
--cc=djwong@kernel.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