From: Jim Fehlig <jfehlig@suse.com>
To: Eric Blake <eblake@redhat.com>, Ian Campbell <ian.campbell@citrix.com>
Cc: libvir-list@redhat.com, xen-devel@lists.xen.org
Subject: Re: [libvirt] [PATCH libvirt] libxl: avoid freeing an uninitialised bitmap
Date: Fri, 19 Jun 2015 13:20:34 -0600 [thread overview]
Message-ID: <55846B82.6040107@suse.com> (raw)
In-Reply-To: <5584495D.9020402@redhat.com>
On 06/19/2015 10:54 AM, Eric Blake wrote:
> On 06/19/2015 10:33 AM, Ian Campbell wrote:
>> If vm->def->cputune.nvcpupin is 0 in libxlDomainSetVcpuAffinities (as
>> seems to be the case on arm) then the VIR_FREE after cleanup: would be
>> operating on an uninitialised pointer in map.map.
>>
>> Fix this by using libxl_bitmap_init and libxl_bitmap_dispose in the
>> appropriate places (like VIR_FREE libxl_bitmap_dispose is also
> s/VIR_FREE/VIR_FREE,/
>
>> idempotent, so there is no double free on exit from the loop).
>>
>> libxl_bitmap_dispose is slightly preferable since it also sets
>> map.size back to 0, avoiding a potential source of confusion.
>>
>> This fixes the crashes we've been seeing in the Xen automated tests on
>> ARM.
>>
>> I had a glance at the handful of other users of libxl_bitmap and none
>> of them looked to have a similar issue.
>>
>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>> ---
>> src/libxl/libxl_domain.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
> ACK.
Modified the commit message as suggested and pushed. Thanks!
Regards,
Jim
prev parent reply other threads:[~2015-06-19 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1434731610-25257-1-git-send-email-ian.campbell@citrix.com>
2015-06-19 16:54 ` [libvirt] [PATCH libvirt] libxl: avoid freeing an uninitialised bitmap Eric Blake
[not found] ` <5584495D.9020402@redhat.com>
2015-06-19 19:20 ` Jim Fehlig [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=55846B82.6040107@suse.com \
--to=jfehlig@suse.com \
--cc=eblake@redhat.com \
--cc=ian.campbell@citrix.com \
--cc=libvir-list@redhat.com \
--cc=xen-devel@lists.xen.org \
/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.