From: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: USB Storage List <usb-storage@one-eyed-alien.net>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: Notify about errors during initialization
Date: Sun, 4 Jan 2004 18:10:47 -0800 [thread overview]
Message-ID: <20040105021047.GD30408@one-eyed-alien.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0312081101480.1043-100000@ida.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]
Did you ever get an answer from the linux-scsi people on this?
Matt
On Mon, Dec 08, 2003 at 11:15:06AM -0500, Alan Stern wrote:
> Cross-posted to the linux-scsi list in the hope that someone there can
> confirm this answer...
>
> On Sat, 6 Dec 2003, Matthew Dharm wrote:
>
> > Question: Are we guaranteed that scsi_scan_host() doesn't return until the
> > scanning process is complete?
>
> I'm not absolutely certain -- best to check with someone on the linux-scsi
> list. But a quick look through the call chain in scsi_scan.c indicates
> that scsi_scan_host() doesn't return until the scanning process is indeed
> complete. The real work is done in scsi_probe_lun() (called from
> scsi_probe_and_add_lun()), and that uses scsi_wait_req(). After all, it
> can't tell whether the LUN is there or not until it gets a reply to the
> INQUIRY!
>
> > I recall a problem that we had with the setting of flags and the call to
> > scan the host -- without pre-emption, it worked, but with pre-emption
> > things happened in the wrong order. Could that happen here?
>
> I don't remember that problem. But I don't think pre-emption would cause
> any difficulties here. All the flags should be set before we call
> scsi_scan_host(). If you can provide more details or a reference to what
> you're thinking of, I could reply in more detail.
>
> When pre-emption does cause a problem it's generally because of some
> assumption that the current task won't be scheduled out when it calls up()
> or complete() or something like that.
>
> Alan Stern
>
>
>
>
>
>
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
I'm just trying to think of a way to say "up yours" without getting fired.
-- Stef
User Friendly, 10/8/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-05 2:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031207051634.GB21951@one-eyed-alien.net>
2003-12-08 16:15 ` Notify about errors during initialization Alan Stern
2004-01-05 2:10 ` Matthew Dharm [this message]
2004-01-05 22:04 ` Alan Stern
2004-01-05 22:13 ` Christoph Hellwig
2004-01-05 23:32 ` Mike Anderson
2004-01-06 16:17 ` Christoph Hellwig
2004-01-06 17:15 ` Patrick Mansfield
2004-01-06 17:18 ` Christoph Hellwig
2004-01-06 18:08 ` Mike Anderson
2004-01-06 18:08 ` Christoph Hellwig
2004-01-06 19:04 ` Mike Anderson
2004-01-06 18:07 ` Sysfs attribute file for max_sectors Alan Stern
2004-01-06 18:23 ` James Bottomley
2004-01-06 19:31 ` Alan Stern
2004-01-06 19:47 ` James Bottomley
2004-01-07 16:16 ` PATCH: (as168) " Alan Stern
2004-01-06 21:11 ` Patrick Mansfield
2004-01-06 21:14 ` Jens Axboe
2004-01-06 22:00 ` Alan Stern
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=20040105021047.GD30408@one-eyed-alien.net \
--to=mdharm-scsi@one-eyed-alien.net \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@one-eyed-alien.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.