Quoting Cole Robinson (2019-04-02 11:22:59) > On 4/1/19 4:58 PM, Michael Roth wrote: > > Hi everyone, > > > > > > The following new patches are queued for QEMU stable v3.0.1: > > > > https://github.com/mdroth/qemu/commits/stable-3.0-staging > > > > The release is planned for 2019-04-11: > > > > https://wiki.qemu.org/Planning/3.0 > > > > Please respond here or CC qemu-sta...@nongnu.org on any patches you > > think should be included in the release. > > > > Note that this update falls outside the normal stable release support > > window (~1 development cycle), but is being release now since it was > > delayed from its intended release date. > > > > Thanks! > > > > Here's some extra patches we are carrying in Fedora 29 > > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-15746 > 6f2231e9b0 seccomp: use SIGSYS signal instead of killing the thread > bda08a5764 seccomp: prefer SCMP_ACT_KILL_PROCESS if available > d0699bd37c configure: require libseccomp 2.2.0 > 70dfabeaa7 seccomp: set the seccomp filter to all threads > > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-18849 > e58ccf0396 lsi53c895a: check message length value is valid > > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-6778 > a907458ad8 slirp: check data length while emulating ident function > > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-18954 > d07945e78e ppc/pnv: check size before data buffer access > > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-19364 > 5b76ef50f6 9p: write lock path in v9fs_co_open2() > 5b3c77aa58 9p: take write lock on fid path updates (CVE-2018-19364)
Thank you for the suggestions so far. I've applied these patches and backed out: target/xtensa: drop num_[core_]regs from dc232b/dc233c configs Changes have been pushed to staging tree: https://github.com/mdroth/qemu/commits/stable-3.0-staging > > Thanks, > Cole >