[OE-core] [PATCH] fixup! qemu: backport patches to fix cves

[Alexey Brodkin]

Hi Kai,

> -----Original Message-----
> From: Kang Kai <Kai.Kang at windriver.com>
> Sent: Thursday, March 21, 2019 6:27 AM
> To: Alexey Brodkin <alexey.brodkin at synopsys.com>
> Cc: openembedded-core at lists.openembedded.org; richard.purdie at linuxfoundation.org
> Subject: Re: [PATCH] fixup! qemu: backport patches to fix cves
> 
> On 2019/3/21 上午5:34, Alexey Brodkin wrote:
> > Hi Kai Kang,
> >
> >> -----Original Message-----
> >> From: kai.kang at windriver.com <kai.kang at windriver.com>
> >> Sent: Wednesday, March 20, 2019 4:16 PM
> >> To: richard.purdie at linuxfoundation.org
> >> Cc: alexey.brodkin at synopsys.com; openembedded-core at lists.openembedded.org
> >> Subject: [PATCH] fixup! qemu: backport patches to fix cves
> > Just wondering if you were able to reproduce mentioned problem
> > on your side before fixing it?
> >
> > Given Richard's input this problem was supposed to be caught
> > before your previous commit hit OE master branch but somehow it
> > slipped through the cracks...
> >
> > Or otherwise my setup should be somehow very special if it only
> > happens for me.
> 
> I can reproduce the build failure with default configure:
> 
> $ . poky/oe-init-build-env
> $ bitbake qemu-system-native
> 
> It should be covered by autobuilder. :(
> 
> And there is no error to build qemu and qemu-native  that
> hw/rdma/rdma_backend.c is not even compiled because:
> 
> * CONFIG_PCI is not set for qemu-native
> * CONFIG_PVRDMA is not set for qemu

Thanks for confirmation!

Richard, FWIW I hit this issue building "build-appliance-image"
which I use for smoke-testing as there're quite a few packages
being built.

-Alexey