| 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
| ||
|
Date: Mon, 15 Oct 2007 13:15:40 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Alan Cox <alan@...rguk.ukuu.org.uk> cc: Ingo Molnar <mingo@...e.hu>, Boaz Harrosh <bharrosh@...asas.com>, Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org, James Bottomley <James.Bottomley@...elEye.com> Subject: Re: [patch] scsi: fix crash in gdth_timeout() 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 - 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/
Powered by blists - more mailing lists