From: yue <kvmluck@163.com>
To: Yadi Hu <yadi.hu@windriver.com>
Cc: stefanha@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] CVE-2016-5403 results in a bug
Date: Thu, 20 Oct 2016 17:43:48 +0800 (CST) [thread overview]
Message-ID: <d09f42a.17acc.157e179a587.Coremail.kvmluck@163.com> (raw)
In-Reply-To: <580735AD.5080409@windriver.com>
i basicly understand the code, i have it done next week.
do you have any suggestion?
At 2016-10-19 16:58:21, "Yadi Hu" <yadi.hu@windriver.com> wrote:
>On 2016年10月18日 17:40, Stefan Hajnoczi wrote:
>> On Tue, Oct 18, 2016 at 10:24 AM, yue <kvmluck@163.com> wrote:
>>> i apply this patch, https://git.centos.org/blob/rpms!!qemu-kvm/6078803a0db76660aef491907f795bb23ad33357/SOURCES!kvm-virtio-error-out-if-guest-exceeds-virtqueue-size.patch;jsessionid=124pfc40q9ejezgb0b5qrnv6m#L33 .
>>> but this patch always results in a bug(bug?). a vm always exits with '2016-10-17T07:33:40.393592Z qemu-kvm: Virtqueue size exceeded', if you suspend and resume . (please refer to https://wiki.openstack.org/wiki/Kvm-Pause-Suspend to see the definiton of suspend and resume in openstack). this operation is very commonly used in openstack. i am not sure if this patch is elegant .
>> Try these patches:
>> bccdef6b1a204db0f41ffb6e24ce373e4d7890d4..58a83c61496eeb0d31571a07a51bc19,
>> 4b7f91ed0270a371e1933efa21ba600b6da23ab9
>>
>
>Yue,
>
>any progress? have you tried the above fixes?
>
>Yadi
next prev parent reply other threads:[~2016-10-20 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 9:24 [Qemu-devel] CVE-2016-5403 results in a bug yue
2016-10-18 9:40 ` Stefan Hajnoczi
2016-10-19 8:58 ` Yadi Hu
2016-10-20 9:43 ` yue [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-17 15:39 yue
2016-10-17 8:19 yue
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=d09f42a.17acc.157e179a587.Coremail.kvmluck@163.com \
--to=kvmluck@163.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=yadi.hu@windriver.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).