mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ishikawa <ishikawa@yk.rim.or.jp>
To: Kurt Garloff <garloff@suse.de>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interesting post from the MC project to linux-kernel. :block while  spinlock held...
Date: Sat, 24 Mar 2001 08:59:43 +0900	[thread overview]
Message-ID: <3ABBE36F.89847A3C@yk.rim.or.jp> (raw)
In-Reply-To: <3AB8E3E8.F3204180@yk.rim.or.jp> <20010322180528.B6264@garloff.casa-etp.nl>

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? Apologies.)

Kurt Garloff wrote:

> 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.
> >
> > 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              <----
>   ^^^^^^^^^^^^^^^^^^^^^^
>
> How do I fond about about details?
>
> R


      reply	other threads:[~2001-03-24  0:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 17:24 Ishikawa
2001-03-22 12:31 ` David Woodhouse
2001-03-22 17:05 ` Kurt Garloff
2001-03-23 23:59   ` Ishikawa [this message]

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=3ABBE36F.89847A3C@yk.rim.or.jp \
    --to=ishikawa@yk.rim.or.jp \
    --cc=garloff@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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®