All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rusty Lynch" <rusty@linux.co.intel.com>
To: <linux-kernel@vger.kernel.org>
Cc: <fault-injection-developer@sourceforge.net>,
	<lclaudio@conectiva.com.br>, <acme@conectiva.com.br>,
	<olive@conectiva.com.br>, <riel@conectiva.com.br>
Subject: [ANNOUNCE] Fault-Injection Test Harness Project
Date: Thu, 12 Dec 2002 21:05:16 -0800	[thread overview]
Message-ID: <000901c2a265$3ad3a260$6901a8c0@amr.corp.intel.com> (raw)

Fault-Injection Test Harness Project
-------------------------------------

I am pleased to announce the formation of a new project for developing a
test harness for inserting faults into a running kernel.  The project is
based at http://fault-injection.sf.net, with a bitkeeper tree hosted at
http://fault-injection.bkbits.net:8080/linux-2.5/, and an IRC channel named
#fi on 206.103.61.170. (The DNS entry for the IRC address is about to
change, but the number should stay the same.)

The project started out to try to validate that a kernel driver was
acceptable for a carrier environment (the "mystical" hardened driver) :).
Now, it has morphed to building a general tool for inserting faults into
any part of the kernel to see if the kernel reacts in a way the test
developer expects.  We have kind of straw man design with some
_very_ early prototype work, but for the most part things are just 
now getting started. I know there are some people on this list that 
have some considerable experience in fault injection on other Unix's, 
and some of you have hinted to me in emails that you might be 
interested in creating some kind of fault injection tool for Linux.  
I just hope I can entice you into joining our efforts (even if you 
only want to give us some directional guidance.)

As mentioned we are developing off of a clone of the 2.5 tree that we
periodically sync.  A CVS tree and snapshots are available from the
sourceforge site for those that do not use bitkeeper, but they will always
lag behind.

        -rustyl




             reply	other threads:[~2002-12-13  4:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13  5:05 Rusty Lynch [this message]
2002-12-13  7:25 ` [Fault-injection-developer] [ANNOUNCE] Fault-Injection Test HarnessProject Yasunori Goto

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='000901c2a265$3ad3a260$6901a8c0@amr.corp.intel.com' \
    --to=rusty@linux.co.intel.com \
    --cc=acme@conectiva.com.br \
    --cc=fault-injection-developer@sourceforge.net \
    --cc=lclaudio@conectiva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olive@conectiva.com.br \
    --cc=riel@conectiva.com.br \
    /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.