From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jaya Kumar <jayakumar.lkml@gmail.com>,
Richard Purdie <rpurdie@rpsys.net>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Clarifying platform_device_unregister
Date: Tue, 1 Apr 2008 10:54:54 -0400 [thread overview]
Message-ID: <20080401104533.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <45a44e480804010047m36a9b8e3p97910308ed5677fb@mail.gmail.com>
On Tue, Apr 01, 2008 at 12:47:54AM -0700, Jaya Kumar wrote:
> On Mon, Mar 31, 2008 at 10:19 PM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > On Mon, Mar 31, 2008 at 09:14:35PM -0400, Jaya Kumar wrote:
> > > mytest_device->dev.platform_data = &mydata;
> >
> > Platform device code does kfree(pdev->dev.platform_data) unpon
> > unregistration, so it is not a good idea to assign address of
> > statically-allocated variable here. You should be using:
> >
> > platform_device_add_data(mytest_device, &mydata, sizeof(mydata));
> >
>
> That's interesting. I noticed though that a lot of platform device
> code assigns a statically allocated structure to platform_data. For
> example:
>
> arch/arm/mach-pxa/corgi_pm.c
> static struct sharpsl_charger_machinfo corgi_pm_machinfo = {
> ...
> }
> corgipm_device->dev.platform_data = &corgi_pm_machinfo;
>
> same with spitz_pm.c.
>
> egrep "platform_data.*=.*\&" *.c shows quite a lot of users doing
> that. I guess most of these below are probably okay since these
> drivers can't be rmmoded.
>
Hmm, are you sure they can't be removed? Why do they all have
module_exit methods?
Even if they can't be unloaded the whole thing will blow to pieces
if registration fails. Consider this:
static int __devinit spitzpm_init(void)
{
int ret;
spitzpm_device = platform_device_alloc("sharpsl-pm", -1);
if (!spitzpm_device)
return -ENOMEM;
spitzpm_device->dev.platform_data = &spitz_pm_machinfo;
ret = platform_device_add(spitzpm_device);
if (ret)
platform_device_put(spitzpm_device);
^^^^^^^^^^^
This will try to kfree(spitzpm_device->dev.platform_data) and it gonna
blow. We need to do spitzpm_device->dev.platform_data = NULL before doing
put.
Also spitzpm_init() shoudl be marked __init, not __devinit and
spitzpm_exit() should be __exit() if it is event needed at all.
Richard, I think you work with spitz and corgi, any comments?
--
Dmitry
next prev parent reply other threads:[~2008-04-01 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 1:14 Jaya Kumar
2008-04-01 5:19 ` Dmitry Torokhov
2008-04-01 7:47 ` Jaya Kumar
2008-04-01 14:54 ` Dmitry Torokhov [this message]
2008-04-02 1:57 ` Jaya Kumar
2008-04-05 12:07 ` Richard Purdie
2008-04-05 11:44 ` Richard Purdie
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=20080401104533.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=jayakumar.lkml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.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
all inboxes | Powered by JetHome®