From: "Emilio G. Cota" <cota@braap.org>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] Double-free due to e5dc1a6c6c
Date: Fri, 19 Jan 2018 21:05:57 -0500 [thread overview]
Message-ID: <20180120020557.GA20269@flamenco> (raw)
In-Reply-To: <0919c2ab-1a62-f96c-1847-d6f95d3326f3@linux.vnet.ibm.com>
On Fri, Jan 19, 2018 at 17:55:27 -0500, Stefan Berger wrote:
> I get double-free memory errors when QEMU terminates due to commit
> e5dc1a6c6c.
>
> The way to reproduce the error is to 1st do a 'system_reset' in the monitor
> and then get into the grub console and do a 'halt' there.
Can you please check whether this is fixed by the patch below?
Was posted yesterday on the list, should be on master soon.
https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg04298.html
Thanks,
Emilio
next prev parent reply other threads:[~2018-01-20 2:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 22:55 [Qemu-devel] Double-free due to e5dc1a6c6c Stefan Berger
2018-01-20 2:05 ` Emilio G. Cota [this message]
2018-01-20 3:26 ` Stefan Berger
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=20180120020557.GA20269@flamenco \
--to=cota@braap.org \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.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).