From: Colin Ian King <colin.king@canonical.com>
To: Frank Rowand <frowand.list@gmail.com>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: overlay: fix memory leak of ovcs on error exit path
Date: Thu, 30 Nov 2017 12:18:02 +0000 [thread overview]
Message-ID: <806a0467-87c8-4100-c7f2-54cfa8732465@canonical.com> (raw)
In-Reply-To: <dcb4e2a4-707b-0ccc-e12b-c6fa4ef251b7@gmail.com>
On 30/11/17 12:14, Frank Rowand wrote:
> On 11/29/17 14:17, Colin King wrote:
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> Currently if the call to of_resolve_phandles fails then then ovcs
>> is not kfree'd on the error exit path. Rather than try and make
>> the clean up exit path more convoluted, fix this by just kfree'ing
>> ovcs at the point of error detection and exit via the same exit
>> path.
>>
>> Detected by CoverityScan, CID#1462296 ("Resource Leak")
>>
>> Fixes: f948d6d8b792 ("of: overlay: avoid race condition between applying multiple overlays")
>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>> ---
>> drivers/of/overlay.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/of/overlay.c b/drivers/of/overlay.c
>> index 53bc9e3f0b98..6c8efe7d8cbb 100644
>> --- a/drivers/of/overlay.c
>> +++ b/drivers/of/overlay.c
>> @@ -708,8 +708,10 @@ int of_overlay_apply(struct device_node *tree, int *ovcs_id)
>> of_overlay_mutex_lock();
>>
>> ret = of_resolve_phandles(tree);
>> - if (ret)
>> + if (ret) {
>> + kfree(ovcs);
>> goto err_overlay_unlock;
>> + }
>>
>> mutex_lock(&of_mutex);
>>
>>
>
> False coverity warning. ovcs is freed in free_overlay_changeset().
>
The error exit path is via err_overlay_unlock:
err_overlay_unlock:
of_overlay_mutex_unlock();
out:
pr_debug("%s() err=%d\n", __func__, ret);
return ret;
..so there is no call to free_overlay_changeset there.
Colin
next prev parent reply other threads:[~2017-11-30 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 19:17 Colin King
2017-11-30 12:14 ` Frank Rowand
2017-11-30 12:18 ` Colin Ian King [this message]
2017-11-30 13:37 ` Frank Rowand
2017-11-30 15:01 ` Frank Rowand
2017-11-30 15:26 ` Rob Herring
2017-11-30 12:50 ` Dan Carpenter
2017-11-30 12:54 ` Colin Ian King
2017-11-30 13:51 ` Geert Uytterhoeven
2017-12-04 15:15 ` Geert Uytterhoeven
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=806a0467-87c8-4100-c7f2-54cfa8732465@canonical.com \
--to=colin.king@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@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®