Hello Garloff-san,
Actually, a good question.
I have been trying to find the details of the verification tool from stanford
but to no avail.
Maybe we should ask the posters from the Stanford directly.
(Oops. I thought I posted this to linux-scsi, but did I post
linux-kernel instead?
On Thu, Mar 22, 2001 at 02:24:56AM +0900, Chiaki Ishikawa wrote:
> --- begin quote ---
> > enclosed are 163 potential bugs in 2.4.1 where blocking functions are
> > called with either interrupts disabled or a spin lock held. The
> > checker works by:
>
> Here's the file manifest. Apologies.
>
>
[EMAIL PROTECTED] said:
> drivers/char/applicom.c
There's a rewrite of this for the new PCI API. Doesn't yet support the ISA
cards because I didn't have one to test with. I'll try to get hold of one
and submit it.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe
[EMAIL PROTECTED] said:
drivers/char/applicom.c
There's a rewrite of this for the new PCI API. Doesn't yet support the ISA
cards because I didn't have one to test with. I'll try to get hold of one
and submit it.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe
On Thu, Mar 22, 2001 at 02:24:56AM +0900, Chiaki Ishikawa wrote:
--- begin quote ---
enclosed are 163 potential bugs in 2.4.1 where blocking functions are
called with either interrupts disabled or a spin lock held. The
checker works by:
Here's the file manifest. Apologies.
Hi,
I suppose that many SCSI maintainers do read the linux-kernel
mailing list. However, just in case, I am quoting one of the
very interesting postings that come from people at Stanford.
They seem to be doing mechanical verification / checking of
linux source code to hunt for potentical bugs. In
Hi,
I suppose that many SCSI maintainers do read the linux-kernel
mailing list. However, just in case, I am quoting one of the
very interesting postings that come from people at Stanford.
They seem to be doing mechanical verification / checking of
linux source code to hunt for potentical bugs. In
7 matches
Mail list logo
