public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: (2.5.23) buffer layer error at buffer.c:2326
Date: Thu, 20 Jun 2002 12:50:36 +0100	[thread overview]
Message-ID: <20020620125036.B3824@redhat.com> (raw)
In-Reply-To: <3D10E358.D82DB604@zip.com.au>; from akpm@zip.com.au on Wed, Jun 19, 2002 at 01:02:32PM -0700

Hi,

On Wed, Jun 19, 2002 at 01:02:32PM -0700, Andrew Morton wrote:

> What this says is: I still need to get down and set up a fault simulator
> and make sure that we're doing all the right things when I/O errors occur.

I've got one for 2.4:

	http://people.redhat.com/sct/patches/testdrive/

The testdrive-1.1-for-2.4.19pre10.patch can do random fault injection,
at pseudo-random intervals of selectable frequency, on reads or writes
or both.  It's a modified loop.o which requires a separate
testdrive.o, and you just losetup it over a block device (or, more
easily, "mount -o loop /dev/foo /mnt/bar".)  

It can trace IOs and will watch for suspicious activity such as
overlapping IOs being submitted.  The fault injection code trips in
before the bh request ever gets to the underlying block device.  

It shouldn't be too hard to adapt it to bio if you want.

Cheers,
 Stephen

  parent reply	other threads:[~2002-06-20 11:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 18:10 (2.5.23) buffer layer error at buffer.c:2326 Zwane Mwaikambo
2002-06-19 20:02 ` Andrew Morton
2002-06-19 20:25   ` Anton Altaparmakov
2002-06-19 21:54   ` Roman Zippel
2002-06-20  6:07   ` Zwane Mwaikambo
2002-06-20 11:50   ` Stephen C. Tweedie [this message]
2002-06-20 13:22     ` Brad Hards
2002-06-20 13:49       ` Dave Jones

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=20020620125036.B3824@redhat.com \
    --to=sct@redhat.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linux.realnet.co.sz \
    /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