From: julia.lawall@lip6.fr (Julia Lawall)
To: linux-arm-kernel@lists.infradead.org
Subject: question about drivers/pinctrl/pinctrl-at91.c
Date: Sat, 8 Dec 2012 16:52:42 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1212081643590.1984@hadrien> (raw)
The function at91_dt_node_to_map in drivers/pinctrl/pinctrl-at91.c
contains the following code:
new_map = devm_kzalloc(pctldev->dev, sizeof(*new_map) * map_num, GFP_KERNEL);
if (!new_map)
return -ENOMEM;
*map = new_map;
*num_maps = map_num;
/* create mux map */
parent = of_get_parent(np);
if (!parent) {
kfree(new_map);
return -EINVAL;
}
This is clearly not correct, because the combination of devm_kzalloc and
kfree risks creating a double free. But I am not sure how best to fix it.
Is the data structure intended to normally exist until the driver's remove
function is called? If so, perhaps the devm_kzalloc is OK. If I just
remove the kfree, then the structure will persist until the remove
function is called, even though there was an error, which is perhaps not
good. So I could change the kfree to devm_kfree?
thanks,
julia
next reply other threads:[~2012-12-08 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 15:52 Julia Lawall [this message]
2012-12-11 8:51 ` question about drivers/pinctrl/pinctrl-at91.c Linus Walleij
2012-12-11 9:04 ` Julia Lawall
2012-12-11 9:08 ` Linus Walleij
2012-12-11 9:59 ` Julia Lawall
2012-12-11 9:06 ` Grant Likely
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.1212081643590.1984@hadrien \
--to=julia.lawall@lip6.fr \
--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