From: James Bottomley <James.Bottomley@SteelEye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Mike Anderson <andmike@us.ibm.com>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: Synchronizing scsi_remove_host and the error handler
Date: Sun, 07 Aug 2005 10:36:41 -0500 [thread overview]
Message-ID: <1123429001.5020.14.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0508071041110.28316-100000@netrider.rowland.org>
On Sun, 2005-08-07 at 10:59 -0400, Alan Stern wrote:
> What sort of synchronization is there between scsi_remove_host and the
> error-handler thread? Offhand I can see two possible problems, depending
> on how the LLD is written:
There isn't any by design.
I think you're not thinking about how this works correctly. What remove
host does is loop over the active devices removing them from visibility
and trying to do a final put on the generic devices before removing the
host from visibility and doing a final put on it.
However, any outstanding user will have a reference and will keep all
the bits of the hierarchy in place until that reference is relinquished.
> In general, there needs to be some way for the error handler to prevent
> the LLD from being unloaded. I don't know what the best answer is. Has
> anyone thought about this?
I take it the problem is that most LLDs go on to release resources (like
interrupts and memory regions) immediately after calling
scsi_remove_host()?
The solution is probably to trigger the resource cleanup from the host
device release method.
James
next prev parent reply other threads:[~2005-08-07 15:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 14:59 Synchronizing scsi_remove_host and the error handler Alan Stern
2005-08-07 15:36 ` James Bottomley [this message]
2005-08-07 18:43 ` Alan Stern
2005-08-07 21:57 ` James Bottomley
2005-08-08 18:24 ` Luben Tuikov
2005-08-08 19:54 ` Mike Anderson
2005-08-08 20:25 ` Luben Tuikov
2005-08-08 20:06 ` Mike Anderson
2005-08-07 22:15 ` Stefan Richter
2005-08-08 20:41 ` Alan Stern
2005-08-08 21:36 ` Mike Anderson
2005-08-08 22:36 ` Alan Stern
2005-08-08 23:10 ` Stefan Richter
2005-08-09 14:23 ` Alan Stern
2005-08-09 19:37 ` Stefan Richter
2005-08-09 20:07 ` Alan Stern
2005-08-09 20:45 ` Stefan Richter
2005-08-08 23:59 ` Stefan Richter
2005-08-09 14:40 ` Alan Stern
2005-08-09 18:21 ` Stefan Richter
2005-08-09 18:49 ` Alan Stern
2005-08-08 21:49 ` Stefan Richter
2005-08-08 22:20 ` Luben Tuikov
2005-08-08 22:30 ` Alan Stern
2005-08-09 0:49 ` Luben Tuikov
2005-08-09 14:50 ` Alan Stern
2005-08-08 22:23 ` James Bottomley
2005-08-08 22:40 ` Alan Stern
2005-08-08 18:07 ` Luben Tuikov
2005-08-08 18:04 ` Luben Tuikov
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=1123429001.5020.14.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=andmike@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.