From: Andries Brouwer <aebr@win.tue.nl>
To: Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] oops in sd_shutdown
Date: Tue, 12 Aug 2003 10:51:37 +0200 [thread overview]
Message-ID: <20030812085137.GA6168@win.tue.nl> (raw)
In-Reply-To: <20030812075353.A18547@infradead.org>
On Tue, Aug 12, 2003 at 07:53:53AM +0100, Christoph Hellwig wrote:
> > I see an Oops in the SCSI code, caused by the fact that sdkp is NULL
> > in sd_shutdown. "How can that be?", you will ask - dev->driver_data was set
> > in sd_probe. But in my case sd_probe never finished. An insmod usb-storage
> > hangs forever, or at least for more than six hours, giving ample opportunity
> > to observe this race between sd_probe and sd_shutdown.
> > (Of course sd_probe hangs in sd_revalidate disk.)
>
> Well, this same problem could show upb in any other driver. Could
> you instead send a patch to Pat that the driver model never calls
> the shutdown method for a driver that hasn't finished ->probe?
Yes, that is the next stage. But it takes a few hours instead of a
few seconds.
next prev parent reply other threads:[~2003-08-12 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.53.0308111426570.16008@thevillage.soulcatcher>
2003-08-11 22:28 ` [PATCH] oops in sd_shutdown Andries Brouwer
2003-08-12 1:13 ` Jeff Woods
2003-08-12 2:49 ` Andries Brouwer
2003-08-12 6:35 ` Jeff Woods
2003-08-12 21:36 ` [linux-usb-devel] " Greg KH
2003-08-12 6:53 ` Christoph Hellwig
2003-08-12 8:51 ` Andries Brouwer [this message]
2003-08-12 21:35 ` [linux-usb-devel] " Greg KH
2003-08-13 0:24 ` Mike Anderson
2003-08-13 10:46 ` Andries Brouwer
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=20030812085137.GA6168@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox