From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [PATCH 0/2] block: null_blk: make fault-injection configurable via configfs
Date: Mon, 27 Mar 2023 22:18:20 +0000 [thread overview]
Message-ID: <7c00f4f8-5bdf-4fa6-d9f0-141cf88c9ec9@nvidia.com> (raw)
In-Reply-To: <ZCIVBNjrmLqvcGBi@infradead.org>
On 3/27/23 15:13, Christoph Hellwig wrote:
> On Mon, Mar 27, 2023 at 11:37:31PM +0900, Akinobu Mita wrote:
>> This patch set makes null_blk driver-specific fault-injection dynamically
>> configurable per device via configfs.
>>
>> Since the null_blk driver supports configuration such as device creation
>> via configfs, it is natural to configure fault-injection via configfs as
>> well.
>>
>> Currently, only the debugfs interface is provided for dynamically
>> configuring fault-injection, so this introduces a compatible interface via
>> configfs.
> Oh, nice. Can you also update blktests to take advantage of this and
> not require built-in null_blk for fault injection tests?
+1 on blktests, please CC me when you do.
-ck
next prev parent reply other threads:[~2023-03-27 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 14:37 Akinobu Mita
2023-03-27 14:37 ` [PATCH 1/2] fault-inject: allow configuration " Akinobu Mita
2023-04-15 14:53 ` Geert Uytterhoeven
2023-04-15 16:50 ` Akinobu Mita
2023-03-27 14:37 ` [PATCH 2/2] block: null_blk: make fault-injection dynamically configurable per device Akinobu Mita
2023-03-27 22:13 ` [PATCH 0/2] block: null_blk: make fault-injection configurable via configfs Christoph Hellwig
2023-03-27 22:18 ` Chaitanya Kulkarni [this message]
2023-03-29 16:21 ` [PATCH blktests] don't require modular null_blk for fault-injection Akinobu Mita
2023-04-12 3:05 ` Shin'ichiro Kawasaki
2023-04-15 10:29 ` Akinobu Mita
2023-04-13 13:39 ` [PATCH 0/2] block: null_blk: make fault-injection configurable via configfs Jens Axboe
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=7c00f4f8-5bdf-4fa6-d9f0-141cf88c9ec9@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®