From: Alex Chen <alex.chen@huawei.com>
To: Raphael Norwitz <raphael.s.norwitz@gmail.com>
Cc: qemu-trivial@nongnu.org, zhang.zhanghailiang@huawei.com,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
QEMU <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] vhost-user-scsi: Fix memleaks in vus_proc_req()
Date: Wed, 25 Nov 2020 09:20:33 +0800 [thread overview]
Message-ID: <5FBDB161.505@huawei.com> (raw)
In-Reply-To: <CAFubqFub7gPiuHAU4fFXPncCZhfM3iPAr-oVDgR3Ewyk_D8hjA@mail.gmail.com>
On 2020/11/24 23:37, Raphael Norwitz wrote:
> On Tue, Nov 24, 2020 at 9:50 AM Alex Chen <alex.chen@huawei.com> wrote:
>>
>> The 'elem' is allocated memory in vu_queue_pop(), and it's memory should be
>> freed in all error branchs after vu_queue_pop().
>
> s/branchs/branches
>
>> In addition, in order to free 'elem' memory outside of while(1) loop, move the
>> definition of 'elem' to the begin of vus_proc_req().
>
> s/begin/beginning
>
>>
>> Reported-by: Euler Robot <euler.robot@huawei.com>
>> Signed-off-by: Alex Chen <alex.chen@huawei.com>
>
> Other than spelling in the commit message, looks good to me.
>
Thanks for your review, I will fix it and send patch v2.
Thanks,
Alex
> Reviewed-by: Raphael Norwitz <raphael.norwitz@nutanix.com>
>
>> ---
>> contrib/vhost-user-scsi/vhost-user-scsi.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/contrib/vhost-user-scsi/vhost-user-scsi.c b/contrib/vhost-user-scsi/vhost-user-scsi.c
>> index 0f9ba4b2a2..4639440a70 100644
>> --- a/contrib/vhost-user-scsi/vhost-user-scsi.c
>> +++ b/contrib/vhost-user-scsi/vhost-user-scsi.c
>> @@ -232,6 +232,7 @@ static void vus_proc_req(VuDev *vu_dev, int idx)
>> VugDev *gdev;
>> VusDev *vdev_scsi;
>> VuVirtq *vq;
>> + VuVirtqElement *elem = NULL;
>>
>> assert(vu_dev);
>>
>> @@ -248,7 +249,6 @@ static void vus_proc_req(VuDev *vu_dev, int idx)
>> g_debug("Got kicked on vq[%d]@%p", idx, vq);
>>
>> while (1) {
>> - VuVirtqElement *elem;
>> VirtIOSCSICmdReq *req;
>> VirtIOSCSICmdResp *rsp;
>>
>> @@ -288,6 +288,7 @@ static void vus_proc_req(VuDev *vu_dev, int idx)
>>
>> free(elem);
>> }
>> + free(elem);
>> }
>>
>> static void vus_queue_set_started(VuDev *vu_dev, int idx, bool started)
>> --
>> 2.19.1
>>
>>
> .
>
prev parent reply other threads:[~2020-11-25 1:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 14:37 [PATCH] vhost-user-scsi: Fix memleaks in vus_proc_req() Alex Chen
2020-11-24 15:37 ` Raphael Norwitz
2020-11-25 1:20 ` Alex Chen [this message]
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=5FBDB161.505@huawei.com \
--to=alex.chen@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=raphael.s.norwitz@gmail.com \
--cc=zhang.zhanghailiang@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).