From: Christoph Hellwig <hch@infradead.org>
To: Anand Jain <anajain.sg@gmail.com>
Cc: Boris Burkov <boris@bur.io>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v3] btrfs: btrfs_log_dev_io_error() on all bio errors
Date: Mon, 6 Apr 2026 23:50:45 -0700 [thread overview]
Message-ID: <adSpRS6uhH5jrTPy@infradead.org> (raw)
In-Reply-To: <66b3a6ae-f035-412c-8683-8f869edad00f@gmail.com>
On Tue, Apr 07, 2026 at 02:47:37PM +0800, Anand Jain wrote:
> BLK_STS_PROTECTION is interpreted differently depending on the device.
> In NVMe, it indicates invalid Protection Information (PI), while in
> HDDs/SSDs it typically points to a malformed CDB (often a software bug).
> This is one of several possible error conditions.
BLK_STS_PROTECTION should never point to a malformed CDB, and my
quick search of the source tree says we don't do that. Where do
you think that happens?
> Rather than introducing new BLK_STS_* codes, vendors have reused
> existing ones for newer device types to maintain backward compatibility.
???
next prev parent reply other threads:[~2026-04-07 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 16:15 [PATCH v3] btrfs: btrfs_log_dev_io_error() on all bio errors Boris Burkov
2026-04-07 5:16 ` Christoph Hellwig
2026-04-07 6:47 ` Anand Jain
2026-04-07 6:50 ` Christoph Hellwig [this message]
2026-04-07 18:01 ` David Sterba
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=adSpRS6uhH5jrTPy@infradead.org \
--to=hch@infradead.org \
--cc=anajain.sg@gmail.com \
--cc=boris@bur.io \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@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