linux-kernel - Re: [patch 0/7] fault-injection capabilities (v5)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061012142625.520d3d87.akpm@osdl.org>
Date:	Thu, 12 Oct 2006 14:26:25 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Akinobu Mita <akinobu.mita@...il.com>
Cc:	linux-kernel@...r.kernel.org, ak@...e.de, Don Mullis <dwm@...r.net>
Subject: Re: [patch 0/7] fault-injection capabilities (v5)

On Thu, 12 Oct 2006 16:43:05 +0900
Akinobu Mita <akinobu.mita@...il.com> wrote:

> Fault-injection capabilities patch set version 5.

It all looks quite nice, thanks.  Couple of things...

You've presumably run a kernel with these various things enabled.  What
happens?  Does the kernel run really slowly?  Does userspace collapse in a
heap?  Does it oops and die?

Also, one place where this infrastructure could be of benefit is in device
drivers: simulate a bad sector on the disk, a pulled cable, a timeout
reading from a status register, etc.  If that works well and is useful then
I can see us encouraging driver developers to wire up fault-injection in
the major drivers.

Hence it would be useful at some stage to go in and to actually do all this
for a particular driver.  As an example implementation for others to
emulate and as a test for the fault-injection infrastructure itself - we
may discover that new capabilities are needed as this work is done.

I wouldn't say this is an urgent thing to be doing, but it is a logical
next step..

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/