From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1151986 <1151986@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1151986] Re: buffer overflow after block-stream via QMP
Date: Fri, 8 Mar 2013 09:45:12 +0100 [thread overview]
Message-ID: <20130308084512.GB8984@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20130307181428.3305.38069.malone@soybean.canonical.com>
On Thu, Mar 07, 2013 at 06:14:27PM -0000, Helge Rausch wrote:
> I cannot reproduce it anymore on master. One option we now have without
> building it ourselves is using 1.4.0 from Ubuntu's raring derivate.
> Would you consider that stable enough for production use (the qemu
> package, not raring)?
QEMU 1.4.0 is a stable release, it is intended for production use.
I can't speak for Ubuntu packaging of QEMU 1.4.0, perhaps check the bug
tracker to see if there are known issues with the package.
Stefan
next prev parent reply other threads:[~2013-03-08 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 11:02 [Qemu-devel] [Bug 1151986] [NEW] buffer overflow after block-stream via QMP Helge Rausch
2013-03-07 16:45 ` Stefan Hajnoczi
2013-03-07 18:14 ` [Qemu-devel] [Bug 1151986] " Helge Rausch
2013-03-08 8:45 ` Stefan Hajnoczi [this message]
2013-03-08 9:21 ` Helge Rausch
2013-03-08 15:32 ` Serge Hallyn
2018-01-10 21:51 ` Thomas Huth
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=20130308084512.GB8984@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=1151986@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 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).