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 the last week or so,
many potential bugs were identified and fixed.
Here is one that might be of interest to SCSI developers.
The checkers are known to produce false positives. So beware.
--- 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.
drivers/atm/idt77105.c
drivers/atm/iphase.c
drivers/atm/uPD98402.c
drivers/block/cciss.c
drivers/block/cpqarray.c
drivers/char/applicom.c
...
drivers/scsi/aha1542.c <--- some scsi files
drivers/scsi/atp870u.c <----
drivers/scsi/psi240i.c <----
drivers/scsi/sym53c416.c <----
drivers/scsi/tmscsim.c <----
...
[the rest omiitted]
--- end quote ---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/