From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [master][krogoth][PATCH 1/2] qemu: Security fix CVE-2016-2857
Date: Fri, 6 May 2016 18:51:33 +0300 [thread overview]
Message-ID: <572CBD85.8040500@linux.intel.com> (raw)
In-Reply-To: <572CBC7E.9080407@gmail.com>
On 05/06/2016 06:47 PM, akuster808 wrote:
> I can not reproduce this issue. I have used two different build systems.
> I have another I will try.
>
> so the testcase be?
>
> 1) bitbake core-image-sato
> 2) runqemu qemux86
3) verify that you have a bunch of .gir and .typelib files on that image
(or in target sysroot)
Alex
next prev parent reply other threads:[~2016-05-06 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 18:23 [master][krogoth][PATCH 1/2] qemu: Security fix CVE-2016-2857 Armin Kuster
2016-04-28 18:23 ` [master][krogoth][PATCH 2/2] qemu: Security fix CVE-2016-2858 Armin Kuster
2016-05-04 9:52 ` [master][krogoth][PATCH 1/2] qemu: Security fix CVE-2016-2857 Joshua G Lock
2016-05-04 9:58 ` Alexander Kanavin
2016-05-04 10:49 ` Joshua G Lock
[not found] ` <572A0450.10100@mvista.com>
2016-05-04 22:17 ` Joshua G Lock
2016-05-06 15:47 ` akuster808
2016-05-06 15:51 ` Alexander Kanavin [this message]
2016-05-09 21:27 ` akuster808
2016-05-10 13:46 ` Joshua G Lock
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=572CBD85.8040500@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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