From: John Snow <jsnow@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, afaerber@suse.de,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/5] libqos: Allow calling guest_free on NULL pointer
Date: Fri, 24 Apr 2015 16:01:35 -0400 [thread overview]
Message-ID: <553AA11F.5040404@redhat.com> (raw)
In-Reply-To: <1429875320-410-3-git-send-email-famz@redhat.com>
On 04/24/2015 07:35 AM, Fam Zheng wrote:
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> tests/libqos/malloc.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tests/libqos/malloc.c b/tests/libqos/malloc.c
> index 67f3190..c15be89 100644
> --- a/tests/libqos/malloc.c
> +++ b/tests/libqos/malloc.c
> @@ -283,6 +283,9 @@ uint64_t guest_alloc(QGuestAllocator *allocator, size_t size)
>
> void guest_free(QGuestAllocator *allocator, uint64_t addr)
> {
> + if (!addr) {
> + return;
> + }
> mlist_free(allocator, addr);
> if (allocator->opts & ALLOC_PARANOID) {
> mlist_check(allocator);
>
Reviewed-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2015-04-24 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 11:35 [Qemu-devel] [PATCH v2 0/5] virtio-test: Test case update Fam Zheng
2015-04-24 11:35 ` [Qemu-devel] [PATCH v2 1/5] tests: Link libqos virtio object to virtio-scsi-test Fam Zheng
2015-04-24 20:02 ` John Snow
2015-04-24 11:35 ` [Qemu-devel] [PATCH v2 2/5] libqos: Allow calling guest_free on NULL pointer Fam Zheng
2015-04-24 20:01 ` John Snow [this message]
2015-04-24 11:35 ` [Qemu-devel] [PATCH v2 3/5] libqos: Complete virtio device ID definition list Fam Zheng
2015-04-24 11:35 ` [Qemu-devel] [PATCH v2 4/5] tests: virtio-scsi: Move start/stop to individual test functions Fam Zheng
2015-04-24 11:35 ` [Qemu-devel] [PATCH v2 5/5] tests: virtio-scsi: Add test for unaligned WRITE SAME Fam Zheng
2015-05-14 6:29 ` [Qemu-devel] [PATCH v2 0/5] virtio-test: Test case update Fam Zheng
2015-06-09 10:13 ` Stefan Hajnoczi
2015-06-17 13:22 ` Paolo Bonzini
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=553AA11F.5040404@redhat.com \
--to=jsnow@redhat.com \
--cc=afaerber@suse.de \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).