From: Julia Lawall <julia.lawall@lip6.fr>
To: Anton Vorontsov <anton@enomsg.org>
Cc: kernel-janitors@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/power/88pm860x_battery.c: use devm_request_threaded_irq
Date: Sun, 6 Jan 2013 09:41:36 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1301060941110.2070@localhost6.localdomain6> (raw)
In-Reply-To: <20130106050953.GH6919@lizard.sbx05280.losalca.wayport.net>
On Sat, 5 Jan 2013, Anton Vorontsov wrote:
> On Sat, Dec 08, 2012 at 06:16:35PM +0100, Julia Lawall wrote:
>> From: Julia Lawall <Julia.Lawall@lip6.fr>
>>
>> devm_request_threaded_irq requests and irq that is freed when a driver
>> detaches. This patch uses devm_request_threaded_irq for irqs that are
>> requested in the probe function of a platform device and are only freed in
>> the remove function.
>>
>> Additionally, the original code used devm_kzalloc, but kfree. This would
>> lead to a double free. The problem was found using the following semantic
>> match (http://coccinelle.lip6.fr/):
>>
>> // <smpl>
>> @@
>> expression x,e;
>> @@
>> x = devm_kzalloc(...)
>> ... when != x = e
>> ?-kfree(x,...);
>> // </smpl>
>>
>> The error handling code in the probe function is also simplified in the
>> cases where there is now nothing to do other than return.
>>
>> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>>
>> ---
> [....]
>> @@ -994,9 +989,6 @@ static int pm860x_battery_remove(struct platform_device *pdev)
>> struct pm860x_battery_info *info = platform_get_drvdata(pdev);
>>
>> power_supply_unregister(&info->battery);
>> - free_irq(info->irq_batt, info);
>> - free_irq(info->irq_cc, info);
>> - kfree(info);
>
> It is not safe to access battery ('struct power_supply') object after
> _unregister() (and irq handlers will surely do). Instead of removing
> free_irq(), the right fix would be to place the two calls before
> _unregister().
Thanks for the feedback. I will send a new patch.
julia
next prev parent reply other threads:[~2013-01-06 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 17:16 Julia Lawall
2013-01-06 5:09 ` Anton Vorontsov
2013-01-06 8:41 ` Julia Lawall [this message]
2013-01-06 8:43 ` [PATCH] drivers/power/88pm860x_battery.c: eliminate possible references to released resources Julia Lawall
2013-01-06 21:16 ` Anton Vorontsov
2013-01-07 6:42 ` Dan Carpenter
2013-01-07 6:48 ` Julia Lawall
2013-01-07 6:53 ` Anton Vorontsov
2013-01-07 7:09 ` Dan Carpenter
2013-01-07 8:00 ` Julia Lawall
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=alpine.DEB.2.02.1301060941110.2070@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=anton@enomsg.org \
--cc=dwmw2@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®