From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/6] xfs: centralize error tag definitions
Date: Tue, 16 Sep 2025 09:46:45 -0700 [thread overview]
Message-ID: <20250916164645.GW8117@frogsfrogsfrogs> (raw)
In-Reply-To: <20250916164057.GA4208@lst.de>
On Tue, Sep 16, 2025 at 06:40:57PM +0200, Christoph Hellwig wrote:
> On Tue, Sep 16, 2025 at 09:38:31AM -0700, Darrick J. Wong wrote:
> > > + * an XFS_ERRTAGS macro that expands to the XFS_ERRTAG macro supplied by the
> > > + * source files that includes this header use for each defined error
> > > + * injection knob.
> >
> > Hmm, that last sentence could be more concise, and describe what is
> > passed to the XFS_ERRTAG macro:
> >
> > "...will define an XFS_ERRTAGS macro that expands to invoke that
> > XFS_ERRTAG macro for each defined error injection knob. The parameters
> > to the XFS_ERRTAG macro are:
> >
> > 1. The XFS_ERRTAG_ flag but without the prefix;
> > 2. The name of the sysfs knob; and
> > 3. The default value for the knob."
>
> That feels a bit too verbose for my taste, but if it helps I can change
> it.
>
> > I wonder if XFS_ERRTAG() should be supplied with the full XFS_ERRTAG_FOO
> > name, not just FOO?
>
> I did this initially, but it means very long lines that make the table
> rather hard to read. So while I'm not a huge fan of magic symbol
> shortening I think it's fine here because the places that need to know
> about it are very confined.
Eh, you're right, there aren't that many places that are going to use
XFS_ERRTAGS. Want to just make the last sentence of the comment read:
"...will define an XFS_ERRTAGS macro that expands to invoke that
XFS_ERRTAG macro for each defined error injection knob."
and then attach
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
next prev parent reply other threads:[~2025-09-16 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 16:28 cleanup error tags v2 Christoph Hellwig
2025-09-16 16:28 ` [PATCH 1/6] xfs: remove xfs_errortag_get Christoph Hellwig
2025-09-16 16:28 ` [PATCH 2/6] xfs: remove xfs_errortag_set Christoph Hellwig
2025-09-16 16:28 ` [PATCH 3/6] xfs: remove the expr argument to XFS_TEST_ERROR Christoph Hellwig
2025-09-16 16:28 ` [PATCH 4/6] xfs: remove pointless externs in xfs_error.h Christoph Hellwig
2025-09-16 16:28 ` [PATCH 5/6] xfs: centralize error tag definitions Christoph Hellwig
2025-09-16 16:38 ` Darrick J. Wong
2025-09-16 16:40 ` Christoph Hellwig
2025-09-16 16:46 ` Darrick J. Wong [this message]
2025-09-16 16:28 ` [PATCH 6/6] xfs: constify xfs_errortag_random_default Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2025-09-15 13:30 cleanup error tags Christoph Hellwig
2025-09-15 13:30 ` [PATCH 5/6] xfs: centralize error tag definitions Christoph Hellwig
2025-09-15 19:10 ` Darrick J. Wong
2025-09-15 20:53 ` Christoph Hellwig
2025-09-15 23:37 ` 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=20250916164645.GW8117@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hch@lst.de \
--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