From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.DE>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch 4/5] fail-injection capability for disk IO
Date: Wed, 23 Aug 2006 21:34:20 +0200 [thread overview]
Message-ID: <eciajs$1ip$1@sea.gmane.org> (raw)
In-Reply-To: 20060823121028.GE5893@suse.de
Jens Axboe <axboe@suse.de> wrote:
> On Wed, Aug 23 2006, Andi Kleen wrote:
>> I think I would prefer a stackable driver instead of this hook.
I second this, preferrably a device-mapper target similar to dm-error.
> But that makes it more tricky to setup a test, since you have to change
> from using /dev/sda (for example) to /dev/stacked-driver.
Do you really think somebody would run such tests on otherwise normally
used devices?
regards
Mario
--
There are two major products that come from Berkeley: LSD and UNIX.
We don't believe this to be a coincidence. -- Jeremy S. Anderson
next prev parent reply other threads:[~2006-08-23 19:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 11:32 [patch 0/5] RFC: fault-injection capabilities Akinobu Mita
2006-08-23 11:32 ` [patch 1/5] fail-injection library Akinobu Mita
2006-08-23 12:09 ` Andi Kleen
2006-08-23 11:32 ` [patch 2/5] fail-injection capability for kmalloc Akinobu Mita
2006-08-23 11:32 ` [patch 3/5] fail-injection capability for alloc_pages() Akinobu Mita
2006-08-23 11:32 ` [patch 4/5] fail-injection capability for disk IO Akinobu Mita
2006-08-23 12:03 ` Jens Axboe
2006-08-23 17:27 ` Andrew Morton
2006-08-23 18:01 ` Jens Axboe
2006-08-23 18:16 ` Ric Wheeler
2006-08-23 18:26 ` Jens Axboe
2006-08-23 18:22 ` Hans Reiser
2006-08-23 12:07 ` Andi Kleen
2006-08-23 12:10 ` Jens Axboe
2006-08-23 19:34 ` Mario 'BitKoenig' Holbe [this message]
2006-08-23 19:42 ` Ric Wheeler
2006-08-23 11:32 ` [patch 5/5] debugfs entries for configuration Akinobu Mita
2006-08-23 12:06 ` [patch 0/5] RFC: fault-injection capabilities Andi Kleen
2006-08-23 14:18 ` Alexey Dobriyan
2006-08-24 18:41 ` Valdis.Kletnieks
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='eciajs$1ip$1@sea.gmane.org' \
--to=mario.holbe@tu-ilmenau.de \
--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