From: James Bottomley <James.Bottomley@SteelEye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Mike Anderson <andmike@us.ibm.com>, Greg KH <greg@kroah.com>,
linux-usb-devel@lists.sourceforge.net,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
mdharm-usb@one-eyed-alien.net
Subject: Re: oops on usb storage device disconnect with 2.6.14-rc1
Date: Thu, 15 Sep 2005 22:27:31 -0400 [thread overview]
Message-ID: <1126837651.4794.16.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0509152133170.9589-100000@netrider.rowland.org>
On Thu, 2005-09-15 at 21:52 -0400, Alan Stern wrote:
> You're forgetting something: Devices can be removed at any time, no matter
> what state the host is in. It's even possible for thread A to be removing
> a device while thread B is removing the host. The A thread will interfere
> with the B thread, because the "list_for_each_entry_safe" loops in
> scsi_forget_host and __scsi_remove_target _aren't_ safe against other
> threads removing devices. Also remember that the list pointers get
> changed when a device is _released_, which can occur quite some time after
> it is _removed_.
>
> In short, those iterations must be carried out as in my patch.
OK, I concede the point ... I'll put it in.
> Finally, having said all that, it turns out there's still a bug in the
> 2.6.14-rc1 code. I feel pretty stupid about it -- you'll understand why
> when you read the patch below.
Heh, yes, got that one in too.
James
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
next prev parent reply other threads:[~2005-09-16 2:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 19:03 oops on usb storage device disconnect with 2.6.14-rc1 Greg KH
2005-09-15 19:23 ` [linux-usb-devel] " Alan Stern
2005-09-15 19:29 ` Greg KH
2005-09-15 19:57 ` James Bottomley
2005-09-15 21:08 ` [linux-usb-devel] " James Bottomley
2005-09-15 22:19 ` Mike Anderson
2005-09-15 22:38 ` [linux-usb-devel] " James Bottomley
2005-09-15 23:55 ` Mike Anderson
2005-09-16 1:46 ` James Bottomley
2005-09-16 1:52 ` [linux-usb-devel] " Alan Stern
2005-09-16 2:27 ` James Bottomley [this message]
2005-09-18 0:36 ` James Bottomley
2005-09-18 2:33 ` [linux-usb-devel] " Alan Stern
2005-09-18 20:00 ` James Bottomley
2005-09-18 0:35 ` James Bottomley
2005-09-18 20:05 ` James Bottomley
2005-09-18 20:37 ` Alan Stern
2005-09-18 22:01 ` [linux-usb-devel] " Greg KH
2005-09-18 22:34 ` Greg KH
2005-09-19 15:19 ` [linux-usb-devel] " James Bottomley
2005-09-20 14:48 ` Greg KH
2005-09-15 23:46 ` [linux-usb-devel] " Greg KH
2005-09-16 1:57 ` 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=1126837651.4794.16.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=andmike@us.ibm.com \
--cc=greg@kroah.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-usb@one-eyed-alien.net \
--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