From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ingo Molnar <mingo@elte.hu>, Boaz Harrosh <bharrosh@panasas.com>,
Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: [patch] scsi: fix crash in gdth_timeout()
Date: Mon, 15 Oct 2007 13:15:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0710151312500.6887@woody.linux-foundation.org> (raw)
In-Reply-To: <20071015210837.311f058a@the-village.bc.nu>
On Mon, 15 Oct 2007, Alan Cox wrote:
>
> For some things. I do it a bit because you can use it to fake
> failures that are tricky to do in the real world. It won't tell you the
> driver works but its suprisingly good for testing for races (forcing IRQ
> delivery at specific points), buggy hardware you don't posess, and things
> like media failures and timeouts your real hardware refuses to do.
Heh. I do agree that you likely find bugs, even if quite often it's
exactly because the behaviour is something that will never happen on real
hardware.
But failure testing is very useful - I forget who it was who debugged some
driver by taking a CD and just scrathing it mercilessly to induce read
errors ;)
Having a really *bad* HW emulator can certainly work that way too, even if
it also would probably end up hitting just a few of the potential error
paths..
Linus
next prev parent reply other threads:[~2007-10-15 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 16:55 Ingo Molnar
2007-10-15 17:08 ` Linus Torvalds
2007-10-15 17:57 ` Jeff Garzik
2007-10-15 18:43 ` Boaz Harrosh
2007-10-15 19:27 ` Ingo Molnar
2007-10-15 19:38 ` Linus Torvalds
2007-10-15 20:08 ` Alan Cox
2007-10-15 20:15 ` Linus Torvalds [this message]
2007-10-15 22:23 ` Ingo Molnar
2007-10-15 19:24 ` Ingo Molnar
2007-10-15 21:55 ` James Bottomley
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=alpine.LFD.0.999.0710151312500.6887@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=James.Bottomley@SteelEye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bharrosh@panasas.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®