From: Aaron Sierra <asierra@xes-inc.com>
To: Daeseok Youn <daeseok.youn@gmail.com>
Cc: martyn welch <martyn.welch@ge.com>,
manohar vanga <manohar.vanga@gmail.com>,
gregkh@linuxfoundation.org, lisa@xenapiadmin.com,
yongjun wei <yongjun_wei@trendmicro.com.cn>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vme: fix memory leak in vme_user_probe()
Date: Wed, 26 Mar 2014 13:51:53 -0500 (CDT) [thread overview]
Message-ID: <1455668003.49319.1395859913516.JavaMail.zimbra@xes-inc.com> (raw)
In-Reply-To: <3217679.sqG7Yrhs8H@daeseok-laptop.cloud.net>
----- Original Message -----
> From: "Daeseok Youn" <daeseok.youn@gmail.com>
> Sent: Tuesday, March 25, 2014 10:01:48 PM
> Subject: [PATCH] staging: vme: fix memory leak in vme_user_probe()
>
>
> If vme_master_request() returns NULL when it failed,
> it need to free buffers for master.
>
> And also removes unreachable code in vme_user_probe().
>
> Signed-off-by: Daeseok Youn <daeseok.youn@gmail.com>
> ---
> drivers/staging/vme/devices/vme_user.c | 9 +++------
> 1 files changed, 3 insertions(+), 6 deletions(-)
Nice catches Daeseok. I don't maintain this driver, but I have some
suggestions below.
>
> diff --git a/drivers/staging/vme/devices/vme_user.c
> b/drivers/staging/vme/devices/vme_user.c
> index 7927927..ffb4eee 100644
> --- a/drivers/staging/vme/devices/vme_user.c
> +++ b/drivers/staging/vme/devices/vme_user.c
> @@ -776,7 +776,8 @@ static int vme_user_probe(struct vme_dev *vdev)
> image[i].kern_buf = kmalloc(image[i].size_buf, GFP_KERNEL);
> if (image[i].kern_buf == NULL) {
> err = -ENOMEM;
> - goto err_master_buf;
> + vme_master_free(image[i].resource);
> + goto err_master;
> }
> }
I think it would be nice to keep all of the cleanup under the err_master
label.
That could be done by changing the kern_buf allocation in this part to
a devm_kmalloc. Then devm handles the kern_buf freeing entirely.
>
> @@ -819,8 +820,6 @@ static int vme_user_probe(struct vme_dev *vdev)
>
> return 0;
>
> - /* Ensure counter set correcty to destroy all sysfs devices */
> - i = VME_DEVS;
> err_sysfs:
> while (i > 0) {
> i--;
> @@ -830,12 +829,10 @@ err_sysfs:
>
> /* Ensure counter set correcty to unalloc all master windows */
> i = MASTER_MAX + 1;
> -err_master_buf:
> - for (i = MASTER_MINOR; i < (MASTER_MAX + 1); i++)
> - kfree(image[i].kern_buf);
> err_master:
> while (i > MASTER_MINOR) {
> i--;
> + kfree(image[i].kern_buf);
> vme_master_free(image[i].resource);
> }
Using devm_kmalloc as mentioned above, the while loop could be
simplified to this:
err_master:
while (i >= MASTER_MINOR) {
vme_master_free(image[i].resource);
i--;
}
If not moving to devm, this should be safe even though the first
kern_buf may be NULL:
err_master:
while (i >= MASTER_MINOR) {
kfree(image[i].kern_buf);
vme_master_free(image[i].resource);
i--;
}
-Aaron
>
> --
> 1.7.4.4
>
>
>
next prev parent reply other threads:[~2014-03-26 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 3:01 Daeseok Youn
2014-03-26 18:51 ` Aaron Sierra [this message]
2014-03-27 1:47 ` DaeSeok Youn
2014-03-27 14:30 ` Aaron Sierra
2014-03-27 23:53 ` DaeSeok Youn
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=1455668003.49319.1395859913516.JavaMail.zimbra@xes-inc.com \
--to=asierra@xes-inc.com \
--cc=daeseok.youn@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa@xenapiadmin.com \
--cc=manohar.vanga@gmail.com \
--cc=martyn.welch@ge.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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
Powered by JetHome