From: Mike Anderson <andmike@us.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Olaf Hering <olh@suse.de>,
linux-usb-devel@lists.sourceforge.net,
linux-scsi@vger.kernel.org, Michael Christie <mikenc@us.ibm.com>
Subject: Re: [linux-usb-devel] 2.6.11-rc3-bk5, oops in scsi_try_bus_reset
Date: Mon, 14 Feb 2005 21:41:24 -0800 [thread overview]
Message-ID: <20050215054124.GB24534@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0502101002120.887-100000@ida.rowland.org>
Alan Stern [stern@rowland.harvard.edu] wrote:
> And Mike Anderson's response was
>
> http://marc.theaimsgroup.com/?l=linux-scsi&m=110538854224319&w=2
>
> His explanation was "Currently scsi_host_cancel being called from
> scsi_remove_host appears to not do anything as scsi_forget_host removes
> the devices from the list it iterates over." I don't know whether this
> problem has been fixed yet.
>
No, this has not been fixed yet, but needs to be.
In discussing this with Mike C today he had a patch that would drain the
devices queues prior to scsi_forget_host returning which may help in this
case.
Along with Mike C's change we could remove the scsi_host_cancel code
(since it does not do anything and when it did it was racey), and shutdown
the error handler thread in scsi_remove_host (reduce possible callers into
the LLDD post scsi_remove_host).
Mike C or I will have something out soon on this.
-andmike
--
Michael Anderson
andmike@us.ibm.com
prev parent reply other threads:[~2005-02-15 7:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 10:56 2.6.11-rc3-bk5, oops in scsi_try_bus_reset Olaf Hering
2005-02-10 15:07 ` [linux-usb-devel] " Alan Stern
2005-02-14 7:20 ` Olaf Hering
2005-02-14 17:07 ` Alan Stern
2005-02-16 13:12 ` Olaf Hering
2005-02-17 18:39 ` Olaf Hering
2005-02-17 19:55 ` Alan Stern
2005-02-17 20:02 ` Olaf Hering
2005-03-02 14:34 ` [linux-usb-devel] " Olaf Hering
2005-03-02 22:20 ` Alan Stern
2005-03-03 12:32 ` [linux-usb-devel] " Olaf Hering
2005-02-15 5:41 ` Mike Anderson [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=20050215054124.GB24534@us.ibm.com \
--to=andmike@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mikenc@us.ibm.com \
--cc=olh@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox