From: Christoph Hellwig <hch@lst.de>
To: alan.adamson@oracle.com
Cc: Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, kbusch@kernel.org,
sagi@grimberg.me, linux-block@vger.kernel.org
Subject: Re: [RFC 0/1] nvme: Add NVMe LBA Fault Injection
Date: Tue, 23 Jan 2024 10:05:06 +0100 [thread overview]
Message-ID: <20240123090506.GA31535@lst.de> (raw)
In-Reply-To: <6874a81c-3f4f-428a-8a95-19898ca004a2@oracle.com>
On Thu, Jan 18, 2024 at 09:02:43AM -0800, alan.adamson@oracle.com wrote:
>
> On 1/17/24 11:24 PM, Christoph Hellwig wrote:
>> On Tue, Jan 16, 2024 at 03:27:27PM -0800, Alan Adamson wrote:
>>> It has been requested that the NVMe fault injector be able to inject faults when accessing
>>> specific Logical Block Addresses (LBA).
>> Curious, but who has requested this? Because injecting errors really
>> isn't the drivers job.
>
>
> It's an application (database) that is requesting it for their error
> handling testing.
Well, how about they then insert it into the real or virtual hardware.
The Linux nvme driver isn't really an error injection framework.
next prev parent reply other threads:[~2024-01-23 9:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 23:27 [RFC 0/1] nvme: Add NVMe LBA Fault Injection Alan Adamson
2024-01-16 23:27 ` [RFC 1/1] " Alan Adamson
2024-01-18 7:24 ` [RFC 0/1] " Christoph Hellwig
2024-01-18 17:02 ` alan.adamson
2024-01-19 4:48 ` Keith Busch
2024-01-23 9:05 ` Christoph Hellwig [this message]
2024-01-23 17:25 ` alan.adamson
2024-01-24 9:04 ` Christoph Hellwig
2024-01-24 16:52 ` alan.adamson
2024-01-24 16:59 ` Keith Busch
2024-01-24 17:11 ` alan.adamson
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 23:10 Alan Adamson
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=20240123090506.GA31535@lst.de \
--to=hch@lst.de \
--cc=alan.adamson@oracle.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.