From: Greg KH <gregkh@suse.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org, Jay Fenlason <fenlason@redhat.com>
Subject: Re: post 2.6.28 regression: device_initialize() now sleeps, and may fail without recovery strategy
Date: Fri, 9 Jan 2009 13:34:03 -0800 [thread overview]
Message-ID: <20090109213403.GA26754@suse.de> (raw)
In-Reply-To: <4967BF99.7010507@s5r6.in-berlin.de>
On Fri, Jan 09, 2009 at 10:20:25PM +0100, Stefan Richter wrote:
> Stefan Richter wrote:
> > Greg KH wrote:
> >> I originally looked at changing this to be at device_add time, but I
> >> think there are some code paths that do device_initialize and then do
> >> some operations on the device before calling device_add.
> >
> > get_device() and put_device() seem to be about the only things that are
> > interesting before device_add().
> >
> > Don't know if a final put_device() in this situation
>
> ...would require dev->p to be present.
But that can be easily handled...
give me a short while to test...
thanks,
greg k-h
next prev parent reply other threads:[~2009-01-09 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 18:35 post 2.6.28 regression: device_initialize() now sleeps, and may fail without recovery strategy Stefan Richter
2009-01-09 19:49 ` [PATCH post 2.6.28] firewire: core: fix sleep in atomic context due to driver core change Stefan Richter
2009-01-09 21:17 ` Alan Cox
2009-01-09 21:54 ` Greg KH
2009-01-09 22:28 ` [git pull] FireWire fix Stefan Richter
2009-01-09 20:56 ` post 2.6.28 regression: device_initialize() now sleeps, and may fail without recovery strategy Greg KH
2009-01-09 21:13 ` Stefan Richter
2009-01-09 21:20 ` Stefan Richter
2009-01-09 21:34 ` Greg KH [this message]
2009-01-09 21:30 ` Greg KH
2009-01-09 21:40 ` Stefan Richter
2009-01-09 21:24 ` Alan Cox
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=20090109213403.GA26754@suse.de \
--to=gregkh@suse.de \
--cc=fenlason@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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