All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: <kuhn.chenqun@huawei.com>
Cc: <qemu-devel@nongnu.org>, <ehabkost@redhat.com>,
	<thuth@redhat.com>, <dgilbert@redhat.com>,
	<qemu-trivial@nongnu.org>, <zhang.zhanghailiang@huawei.com>
Subject: Re: [PATCH v2] test-vmstate: Fix memleaks in test_load_qlist
Date: Thu, 27 Feb 2020 19:03:12 +0100	[thread overview]
Message-ID: <87k147di1r.fsf@secure.laptop> (raw)
In-Reply-To: <20200220134103.26224-1-kuhn.chenqun@huawei.com> (kuhn chenqun's message of "Thu, 20 Feb 2020 21:41:03 +0800")

<kuhn.chenqun@huawei.com> wrote:
> From: Chen Qun <kuhn.chenqun@huawei.com>
>
> There is memleak in test_load_qlist().It's not a big deal,
> but test-vmstate will fail if sanitizers is enabled.
>
> In addition, "ret" is written twice with the same value
>  in test_gtree_load_iommu().
>
> Reported-by: Euler Robot <euler.robot@huawei.com>
> Signed-off-by: Chen Qun <kuhn.chenqun@huawei.com>

Reviewed-by: Juan Quintela <quintela@redhat.com>

queued



WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: <kuhn.chenqun@huawei.com>
Cc: thuth@redhat.com, zhang.zhanghailiang@huawei.com,
	qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
	dgilbert@redhat.com, ehabkost@redhat.com
Subject: Re: [PATCH v2] test-vmstate: Fix memleaks in test_load_qlist
Date: Thu, 27 Feb 2020 19:03:12 +0100	[thread overview]
Message-ID: <87k147di1r.fsf@secure.laptop> (raw)
In-Reply-To: <20200220134103.26224-1-kuhn.chenqun@huawei.com> (kuhn chenqun's message of "Thu, 20 Feb 2020 21:41:03 +0800")

<kuhn.chenqun@huawei.com> wrote:
> From: Chen Qun <kuhn.chenqun@huawei.com>
>
> There is memleak in test_load_qlist().It's not a big deal,
> but test-vmstate will fail if sanitizers is enabled.
>
> In addition, "ret" is written twice with the same value
>  in test_gtree_load_iommu().
>
> Reported-by: Euler Robot <euler.robot@huawei.com>
> Signed-off-by: Chen Qun <kuhn.chenqun@huawei.com>

Reviewed-by: Juan Quintela <quintela@redhat.com>

queued



  parent reply	other threads:[~2020-02-27 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 13:41 [PATCH v2] test-vmstate: Fix memleaks in test_load_qlist kuhn.chenqun
2020-02-20 13:41 ` kuhn.chenqun
2020-02-20 14:06 ` Laurent Vivier
2020-02-20 14:06   ` Laurent Vivier
2020-02-27 18:03 ` Juan Quintela [this message]
2020-02-27 18:03   ` Juan Quintela

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=87k147di1r.fsf@secure.laptop \
    --to=quintela@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kuhn.chenqun@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.