linux-kernel - Re: [patch] scsi: fix crash in gdth

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 15 Oct 2007 21:27:03 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Boaz Harrosh <bharrosh@...asas.com>
Cc:	Jeff Garzik <jeff@...zik.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	James Bottomley <James.Bottomley@...elEye.com>
Subject: Re: [patch] scsi: fix crash in gdth_timeout()

* Boaz Harrosh <bharrosh@...asas.com> wrote:

> > Honestly, the driver is probably rarely run by people that lack the 
> > hardware, I bet...
> 
> It was all "flight by instruments only". I called for HW testers and 
> none came forward. All these changes, apart from "successful downgrade 
> to messy" where also needed in order to push important changes to 
> scsi.
> 
> But a little bird said that QEMU might simulate this HW. SO I guess it 
> is QEMU time for me.

heh. Incidentally i was thinking about using KVM for automated testing. 
Important pieces of hardware should get an in-KVM simulator/emulator, 
that way developers who do not own that hardware can do functionality 
testing too. So basically the highest-quality drivers would have an 
"inverse driver" in KVM, which simulates the hardware. (that model is 
evidently useful to the hardware maker even for new hardware: it can 
then also be used to test the Linux compatibility and Linux performance 
of future planned releases of the hardware, etc.)

	Ingo
-
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/