From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Jarek Poplawski <jarkao2@o2.pl>,
Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [ANNOUNCE] Linux Kernel Tester’s Guide v0.3-rc1
Date: Thu, 21 Jun 2007 14:13:52 +0530 [thread overview]
Message-ID: <467A3A48.6050809@linux.vnet.ibm.com> (raw)
In-Reply-To: <6bffcb0e0706210130h227dcd62n52f34e45dfd8e818@mail.gmail.com>
Michal Piotrowski wrote:
> Hi Balbir,
>
> On 21/06/07, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>> Wonderful! Are there any plans to start using the fault injection
>> framework
>> to catch more defects?
>
> There are plans for the second part called "debugging techniques", but
> I really don't know when I'll start writing this.
>
> In fact I don't even know if it will be useful for testers. IMHO it is
> for developers not for testers.
>
> Regards,
> Michal
>
I thought so too, but being able to randomly fail allocations on a system
might expose the system error handling and recovery capabilities.
It'll also be interesting to see if testing is catching bugs, that tools
(such as sparse) could have caught.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2007-06-21 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 20:11 [ANNOUNCE] Linux Kernel Tester’s Guide v0.3-rc1 Michal Piotrowski
2007-06-19 12:39 ` Clemens Koller
2007-06-19 16:16 ` Michal Piotrowski
2007-06-28 10:49 ` Clemens Koller
2007-06-21 6:50 ` Jan Engelhardt
2007-06-22 8:30 ` [ANNOUNCE] Linux Kernel Tester???s " Jarek Poplawski
2007-06-22 10:52 ` Jarek Poplawski
[not found] ` <661de9470706210031s36396c31xff5428ff60042073@mail.gmail.com>
2007-06-21 8:30 ` [ANNOUNCE] Linux Kernel Tester’s " Michal Piotrowski
2007-06-21 8:43 ` Balbir Singh [this message]
2007-06-23 14:58 ` Rolf Eike Beer
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=467A3A48.6050809@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=bzolnier@gmail.com \
--cc=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=maciej.rutecki@gmail.com \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=rjw@sisk.pl \
/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.