From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: Hard Lockup on 2.4.16 with Via ieee1394 (sbp2 mode)
Date: Fri, 28 Dec 2001 21:11:13 -0800 [thread overview]
Message-ID: <20011228211113.A15125@one-eyed-alien.net> (raw)
In-Reply-To: <200112290321.fBT3GCSs007627@svr3.applink.net> <3C2D3DBB.6ADE1CC5@zip.com.au>, <3C2D3DBB.6ADE1CC5@zip.com.au>; <20011228204041.A14736@one-eyed-alien.net> <3C2D4DA5.E688FF43@zip.com.au>
In-Reply-To: <3C2D4DA5.E688FF43@zip.com.au>; from akpm@zip.com.au on Fri, Dec 28, 2001 at 08:59:17PM -0800
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
It should be using scsi_done()... it actually seems to use whatever was
given as a done function at the queuecommand point, which is, I think,
scsi_done().
Matt
On Fri, Dec 28, 2001 at 08:59:17PM -0800, Andrew Morton wrote:
> Matthew Dharm wrote:
> >
> > Hrm...
> >
> > Does this apply to usb-storage also? Under what conditions do you need to
> > hold the io_request_lock when calling the done function?
> >
>
> That's scsi_old_done(). I don't think scsi_done() cares whether
> io_request_lock is held or not.
>
> And io_request_lock *must* be held by the caller of scsi_old_done() - it
> assumes this. I think we'd have heard by now if usb was getting this
> wrong. Looks like it's using scsi_done(), yes?
>
> -
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
Sir, for the hundreth time, we do NOT carry 600-round boxes of belt-fed
suction darts!
-- Salesperson to Greg
User Friendly, 12/30/1997
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-12-29 5:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 3:13 Timothy Covell
2001-12-29 3:51 ` Andrew Morton
2001-12-29 4:40 ` Matthew Dharm
2001-12-29 4:59 ` Andrew Morton
2001-12-29 5:11 ` Matthew Dharm [this message]
2001-12-29 6:17 ` Timothy Covell
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=20011228211113.A15125@one-eyed-alien.net \
--to=mdharm-kernel@one-eyed-alien.net \
--cc=akpm@zip.com.au \
--cc=linux-kernel@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
Powered by JetHome