From: Andries Brouwer <aebr@win.tue.nl>
To: Greg KH <greg@kroah.com>, 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: Wed, 13 Aug 2003 12:46:19 +0200 [thread overview]
Message-ID: <20030813104619.GA7421@win.tue.nl> (raw)
In-Reply-To: <20030813002450.GA8712@beaverton.ibm.com>
On Tue, Aug 12, 2003 at 05:24:50PM -0700, Mike Anderson wrote:
> > > 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?
> >
> > I think it already will not do that due to taking the bus->subsys.rwsem
> > before calling either probe() or remove().
>
> Is the shutdown being called directly? The shutdown call is protected by
> a different rwsem. Depending on the call graph setting dev->driver on
> return of probe may provide a solution.
Yes, that is precisely what I had considered doing.
> I have not looked at all probe
> routines to understand if this would cause any bad side effects.
>
> Andries,
> Can you send the oops output?
top of stack was reported as (process reboot):
sd_shutdown + 0x22/0x110 NULL deref (namely, sdkp)
i8042_notify_sys
device_shutdown
sys_reboot
do_clock_nanosleep
prev parent reply other threads:[~2003-08-13 10:46 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
2003-08-12 21:35 ` [linux-usb-devel] " Greg KH
2003-08-13 0:24 ` Mike Anderson
2003-08-13 10:46 ` Andries Brouwer [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=20030813104619.GA7421@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=greg@kroah.com \
--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