From: Alexey Brodkin <alexey.brodkin@synopsys.com>
To: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: qemu: backport patches to fix cves breaks qemu-system-native
Date: Wed, 20 Mar 2019 12:07:19 +0000 [thread overview]
Message-ID: <4881796E12491D4BB15146FE0209CE6468224CEA@de02wembxa.internal.synopsys.com> (raw)
In-Reply-To: <861e1a12b82944f7a363d4f6f10b8f54340df1fb.camel@linuxfoundation.org>
Hi Richard,
> -----Original Message-----
> From: richard.purdie@linuxfoundation.org <richard.purdie@linuxfoundation.org>
> Sent: Wednesday, March 20, 2019 3:04 PM
> To: Alexey Brodkin <alexey.brodkin@synopsys.com>; Kai Kang <kai.kang@windriver.com>
> Cc: Patches and discussions about the oe-core layer <openembedded-core@lists.openembedded.org>
> Subject: Re: qemu: backport patches to fix cves breaks qemu-system-native
>
> On Wed, 2019-03-20 at 07:42 +0000, Alexey Brodkin wrote:
> > Hello Kai Kang,
> >
> > You recent changes in QEMU [1] lead to build failure:
> > -------------------------------------->8-----------------------------
> > --------
> > # bitbake qemu-system-native
> > ...
> > > .../build/tmp-glibc/work/x86_64-linux/qemu-system-native/3.1.0-
> > > r0/qemu-3.1.0/hw/rdma/rdma_backend.c:316:42: error:
> > > 'VENDOR_ERR_INV_NUM_SGE' undeclared (first use in this function)
> > > comp_handler(IBV_WC_GENERAL_ERR, VENDOR_ERR_INV_NUM_SGE,
> > > ctx);
> > > ^
> > -------------------------------------->8-----------------------------
> > --------
> >
> > That's obviously because of meta/recipes-devtools/qemu/qemu/0015-fix-
> > CVE-2018-20124.patch.
> >
> > I'm wondering if you tried to build QEMU yourself?
>
> We're not seeing this on the autobuilder, is this gated by some non-
> default config option?
Maybe.
But if you grep by qemu sources you may notice that indeed
VENDOR_ERR_INV_NUM_SGE is not defined anywhere. So regardless of my setup
that looks like a valid and expected build failure.
At least that was the case after I fetched OE-core changes this morning.
-Alexey
next prev parent reply other threads:[~2019-03-20 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 7:42 qemu: backport patches to fix cves breaks qemu-system-native Alexey Brodkin
2019-03-20 8:25 ` Kang Kai
2019-03-20 12:04 ` richard.purdie
2019-03-20 12:07 ` Alexey Brodkin [this message]
2019-03-20 12:08 ` richard.purdie
2019-03-20 12:12 ` Alexey Brodkin
2019-03-20 14:52 ` richard.purdie
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=4881796E12491D4BB15146FE0209CE6468224CEA@de02wembxa.internal.synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.