linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	linux-usb-devel@lists.sourceforge.net,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	mdharm-usb@one-eyed-alien.net
Subject: Re: [linux-usb-devel] oops on usb storage device disconnect with 2.6.14-rc1
Date: Thu, 15 Sep 2005 16:46:12 -0700	[thread overview]
Message-ID: <20050915234612.GA10974@kroah.com> (raw)
In-Reply-To: <1126818483.4821.60.camel@mulgrave>

On Thu, Sep 15, 2005 at 05:08:03PM -0400, James Bottomley wrote:
> On Thu, 2005-09-15 at 15:57 -0400, James Bottomley wrote:
> > I haven't had time to review the eh changes, but I was going to reply to
> > the other one (basically there's a better way to try to close the device
> > add/host remove race using the host state model).
> > 
> > Let me complete the SCSI process and I'll take them through the scsi-rc-
> > fixes tree.
> 
> Well, I think the symptoms are racing scsi_remove_host() calls and the
> solution is to enforce the state model on removal (as in if the host is
> already in the remove state, don't try to remove it again).
> 
> Could you try the patch here:
> 
> http://marc.theaimsgroup.com/?l=linux-scsi&m=112613077011571
> 
> And see if it will fix the problem?

That helped in that there is no more kernel oops.  But the
/sys/block/sdb device (and partitions) do not get removed from the
kernel.  So the next time I plug the device in, it gets bumped to "sdc".
I can provide kernel logs of the unplug event if you wish.

thanks,

greg k-h

  parent reply	other threads:[~2005-09-15 23:46 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
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         ` Greg KH [this message]
2005-09-16  1:57           ` [linux-usb-devel] " 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=20050915234612.GA10974@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@SteelEye.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;
as well as URLs for NNTP newsgroup(s).