From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@redhat.com>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Donald Douwsma <ddouwsma@redhat.com>
Subject: Re: [PATCH RFC] xfs: remap block layer ENODATA read errors to EIO
Date: Tue, 19 Aug 2025 07:48:24 -0700 [thread overview]
Message-ID: <aKSOuIZ7sp0KMI51@infradead.org> (raw)
In-Reply-To: <20250819143443.GA7965@frogsfrogsfrogs>
On Tue, Aug 19, 2025 at 07:34:43AM -0700, Darrick J. Wong wrote:
> Maybe xfs should translate bi_status into whatever error codes it wants
> directly instead of relying on blk_status_to_errno, which can change in
> subtle ways?
We could do that. In fact that's what I'm effectively suggesting.
Pick the ones we care about (and document why while we're at it) and
map everything else to -EIO.
next prev parent reply other threads:[~2025-08-19 14:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 20:22 [PATCH RFC] xfs: remap block layer ENODATA read errors to EIO Eric Sandeen
2025-08-18 20:45 ` Darrick J. Wong
2025-08-18 21:11 ` Eric Sandeen
2025-08-18 23:04 ` Darrick J. Wong
2025-08-21 9:16 ` Donald Douwsma
2025-08-21 9:29 ` [PATCH] xfs: test case for handling io errors when reading extended attributes Donald Douwsma
2025-08-21 12:52 ` [PATCH RFC] xfs: remap block layer ENODATA read errors to EIO Carlos Maiolino
2025-08-21 20:06 ` Eric Sandeen
2025-08-22 7:38 ` Donald Douwsma
2025-08-18 22:09 ` Dave Chinner
2025-08-19 2:27 ` Eric Sandeen
2025-08-19 8:08 ` Christoph Hellwig
2025-08-19 14:34 ` Darrick J. Wong
2025-08-19 14:48 ` Christoph Hellwig [this message]
2025-08-19 15:14 ` Eric Sandeen
2025-08-19 15:23 ` Christoph Hellwig
2025-08-19 15:38 ` Eric Sandeen
2025-08-19 15:41 ` Christoph Hellwig
2025-08-19 21:45 ` Dave Chinner
2025-08-20 0:16 ` Eric Sandeen
2025-08-25 7:51 ` 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=aKSOuIZ7sp0KMI51@infradead.org \
--to=hch@infradead.org \
--cc=ddouwsma@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.