From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: "A. Wilcox" <AWilcox@wilcox-tech.com>,
Andrey Albershteyn <aalbersh@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs_scrub: fix strerror_r usage yet again
Date: Fri, 19 Sep 2025 07:47:30 -0700 [thread overview]
Message-ID: <aM1tAlLshkg7Hi3b@infradead.org> (raw)
In-Reply-To: <20250918194836.GK8096@frogsfrogsfrogs>
On Thu, Sep 18, 2025 at 12:48:36PM -0700, Darrick J. Wong wrote:
> "Fix" this standards body own goal by casting the return value to
> intptr_t and employing some gross heuristics to guess at the location of
> the actual error string.
That really makes things worse. I think we'll just want ifdefs for the
two versions if there is no better option.
next prev parent reply other threads:[~2025-09-19 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 19:48 [PATCH] xfs_scrub: fix strerror_r usage yet again Darrick J. Wong
2025-09-19 14:47 ` Christoph Hellwig [this message]
2025-09-19 16:06 ` 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=aM1tAlLshkg7Hi3b@infradead.org \
--to=hch@infradead.org \
--cc=AWilcox@wilcox-tech.com \
--cc=aalbersh@redhat.com \
--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