From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] base: power: wakeirq: don't leak dev->power.wakeirq
Date: Tue, 7 Jul 2015 03:11:20 -0500 [thread overview]
Message-ID: <20150707081120.GA15545@saruman.tx.rr.com> (raw)
In-Reply-To: <20150707074053.GO10705@atomide.com>
On Tue, Jul 07, 2015 at 12:40:53AM -0700, Tony Lindgren wrote:
> * Rafael J. Wysocki <rjw@rjwysocki.net> [150706 15:49]:
> > On Monday, July 06, 2015 01:01:18 PM Felipe Balbi wrote:
> > > on a first call to dev_pm_attach_wake_irq(), if it
> > > fails, it will leave dev->power.wakeirq set to a
> > > dangling pointer. Instead, let's clear it to make
> > > sure a subsequent call to dev_pm_attach_wake_irq()
> > > has chance to succeed.
> > >
> > > Cc: Tony Lindgren <tmlind@atomide.com>
> > > Signed-off-by: Felipe Balbi <balbi@ti.com>
> > > ---
> > > drivers/base/power/wakeirq.c | 9 ++++++++-
> > > 1 file changed, 8 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/base/power/wakeirq.c b/drivers/base/power/wakeirq.c
> > > index 7470004ca810..394d250a1ad8 100644
> > > --- a/drivers/base/power/wakeirq.c
> > > +++ b/drivers/base/power/wakeirq.c
> > > @@ -50,9 +50,16 @@ static int dev_pm_attach_wake_irq(struct device *dev, int irq,
> > >
> > > err = device_wakeup_attach_irq(dev, wirq);
> > > if (err)
> > > - return err;
> > > + goto err_cleanup;
> > >
> > > return 0;
> > > +
> > > +err_cleanup:
> > > + spin_lock_irqsave(&dev->power.lock, flags);
> > > + dev->power.wakeirq = NULL;
> > > + spin_unlock_irqrestore(&dev->power.lock, flags);
> > > +
> > > + return err;
> > > }
> >
> > Too many labels for me and the fact that acquiring of the lock again in the error
> > patch doesn't look good.
> >
> > However, we can do the entire device_wakeup_attach_irq() under the lock (after
> > removing the locking from it), because we're its only caller.
> >
> > So what about the below instead (build-tested only)?
>
> Nice, still works for me and simplifies things:
>
> Tested-by: Tony Lindgren <tony@atomide.com>
Cool, thanks for testing Tony. Rafael, I'm fine with your version too.
FWIW:
Reported-by: Felipe Balbi <balbi@ti.com>
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150707/fbd9c922/attachment.sig>
next prev parent reply other threads:[~2015-07-07 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 18:01 [PATCH] base: power: wakeirq: don't leak dev->power.wakeirq Felipe Balbi
[not found] ` <CAOf5uwnj=0m99E96k-+AYu68yE_UnX1WVU-=6y7OvJnfXKh8+g@mail.gmail.com>
2015-07-06 18:09 ` Felipe Balbi
2015-07-07 4:17 ` Michael Trimarchi
2015-07-06 23:13 ` Rafael J. Wysocki
2015-07-07 7:40 ` Tony Lindgren
2015-07-07 8:11 ` Felipe Balbi [this message]
2015-07-07 11:11 ` Rafael J. Wysocki
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=20150707081120.GA15545@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).