From: Hans de Goede <hdegoede@redhat.com>
To: Navid Emamdoost <navid.emamdoost@gmail.com>
Cc: emamd001@umn.edu, smccaman@umn.edu, kjlu@umn.edu,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] virt: vbox: fix memory leak in hgcm_call_preprocess_linaddr
Date: Tue, 1 Oct 2019 08:15:23 +0200 [thread overview]
Message-ID: <48a2ad9b-bcdb-6146-0911-37961e07b1d9@redhat.com> (raw)
In-Reply-To: <20190930204223.3660-1-navid.emamdoost@gmail.com>
Hi,
On 30-09-2019 22:42, Navid Emamdoost wrote:
> In hgcm_call_preprocess_linaddr memory is allocated for bounce_buf but
> is not released if copy_form_user fails. In order to prevent memory leak
> in case of failure, the assignment to bounce_buf_ret is moved before the
> error check. This way the allocated bounce_buf will be released by the
> caller.
>
> Fixes: 579db9d45cb4 ("virt: Add vboxguest VMMDEV communication code")
> Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Thank you.
Patch looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
> ---
> drivers/virt/vboxguest/vboxguest_utils.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/virt/vboxguest/vboxguest_utils.c b/drivers/virt/vboxguest/vboxguest_utils.c
> index 75fd140b02ff..43c391626a00 100644
> --- a/drivers/virt/vboxguest/vboxguest_utils.c
> +++ b/drivers/virt/vboxguest/vboxguest_utils.c
> @@ -220,6 +220,8 @@ static int hgcm_call_preprocess_linaddr(
> if (!bounce_buf)
> return -ENOMEM;
>
> + *bounce_buf_ret = bounce_buf;
> +
> if (copy_in) {
> ret = copy_from_user(bounce_buf, (void __user *)buf, len);
> if (ret)
> @@ -228,7 +230,6 @@ static int hgcm_call_preprocess_linaddr(
> memset(bounce_buf, 0, len);
> }
>
> - *bounce_buf_ret = bounce_buf;
> hgcm_call_add_pagelist_size(bounce_buf, len, extra);
> return 0;
> }
>
next prev parent reply other threads:[~2019-10-01 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 23:04 [PATCH] " Navid Emamdoost
2019-09-28 9:54 ` Hans de Goede
2019-09-30 2:22 ` Navid Emamdoost
2019-09-30 8:22 ` Hans de Goede
2019-09-30 20:42 ` [PATCH v2] " Navid Emamdoost
2019-10-01 6:15 ` Hans de Goede [this message]
2019-09-30 20:43 ` [PATCH] " Navid Emamdoost
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=48a2ad9b-bcdb-6146-0911-37961e07b1d9@redhat.com \
--to=hdegoede@redhat.com \
--cc=arnd@arndb.de \
--cc=emamd001@umn.edu \
--cc=gregkh@linuxfoundation.org \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=navid.emamdoost@gmail.com \
--cc=smccaman@umn.edu \
/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®