Message ID | 20191001234616.7825-1-mdroth@linux.vnet.ibm.com (mailing list archive) |
---|---|
Headers | show |
Series | Patch Round-up for stable 4.0.1, freeze on 2019-10-10 | expand |
On 02/10/2019 01.44, Michael Roth wrote: > Hi everyone, > > The following new patches are queued for QEMU stable v4.0.1: > > https://github.com/mdroth/qemu/commits/stable-4.0-staging > > The release is planned for 2019-10-17: > > https://wiki.qemu.org/Planning/4.0 > > Please respond here or CC qemu-stable@nongnu.org on any patches you > think should be included in the release. > Would it make sense to include the slirp update: e1a4a24d262ba5ac74ea1795adb3ab1cd574c7fb "slirp: update with CVE-2019-14378 fix" ? And maybe these commits: 22235bb609c18547cf6b215bad1f9d2ec56ad371 "pc-dimm: fix crash when invalid slot number is used" 95667c3be0c9f5fc62f58fe845879250f63f7d32 "nvme: Set number of queues later in nvme_init()" c0bccee9b40ec58c9d165b406ae3d4f63652ce53 "hw/ssi/mss-spi: Avoid crash when reading empty RX FIFO" a09ef5040477643a7026703199d8781fe048d3a8 "hw/display/xlnx_dp: Avoid crash when reading empty RX FIFO" Thomas
Quoting Thomas Huth (2019-10-01 23:40:49) > On 02/10/2019 01.44, Michael Roth wrote: > > Hi everyone, > > > > The following new patches are queued for QEMU stable v4.0.1: > > > > https://github.com/mdroth/qemu/commits/stable-4.0-staging > > > > The release is planned for 2019-10-17: > > > > https://wiki.qemu.org/Planning/4.0 > > > > Please respond here or CC qemu-stable@nongnu.org on any patches you > > think should be included in the release. > > > Would it make sense to include the slirp update: > > e1a4a24d262ba5ac74ea1795adb3ab1cd574c7fb > "slirp: update with CVE-2019-14378 fix" 4.0 hadn't yet moved to using slirp submodule, but the following patches are included here and should provide the equivalent fixes: slirp: ip_reass: Fix use after free slirp: Fix heap overflow in ip_reass on big packet input > > ? > > And maybe these commits: > > 22235bb609c18547cf6b215bad1f9d2ec56ad371 > "pc-dimm: fix crash when invalid slot number is used" > > 95667c3be0c9f5fc62f58fe845879250f63f7d32 > "nvme: Set number of queues later in nvme_init()" > > c0bccee9b40ec58c9d165b406ae3d4f63652ce53 > "hw/ssi/mss-spi: Avoid crash when reading empty RX FIFO" > > a09ef5040477643a7026703199d8781fe048d3a8 > "hw/display/xlnx_dp: Avoid crash when reading empty RX FIFO" Applied, thanks! > > Thomas >
On 10/2/19 1:44 AM, Michael Roth wrote: > Hi everyone, > > The following new patches are queued for QEMU stable v4.0.1: > > https://github.com/mdroth/qemu/commits/stable-4.0-staging > > The release is planned for 2019-10-17: > > https://wiki.qemu.org/Planning/4.0 > > Please respond here or CC qemu-stable@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 released now since it was > delayed from its intended release date. This commit fix data corruption introduced by ee5d0f89de3: commit 04da973501b591525ce68c2925c61c8886badd4d Author: Li Qiang <liq3ea@163.com> Date: Wed Apr 24 07:06:41 2019 -0700 hw/nvram/fw_cfg: Store 'reboot-timeout' as little endian
Michael Roth <mdroth@linux.vnet.ibm.com> writes: > Hi everyone, > > The following new patches are queued for QEMU stable v4.0.1: > > https://github.com/mdroth/qemu/commits/stable-4.0-staging > > The release is planned for 2019-10-17: > > https://wiki.qemu.org/Planning/4.0 Hi, How about commit fd392cfa8e6fb0dc34bd0327fc356dfbf6edf1fd Author: Yury Kotov <yury-kotov@yandex-team.ru> Date: Mon Apr 8 14:33:43 2019 +0300 migration: Fix use-after-free during process exit commit ebb6ff25cd888a52a64a9adc3692541c6d1d9a42 Author: Philippe Mathieu-Daudé <philmd@redhat.com> Date: Fri Aug 16 19:15:03 2019 +0200 virtio-blk: Cancel the pending BH when the dataplane is reset and https://lists.nongnu.org/archive/html/qemu-devel/2019-09/msg04618.html ?
Hi Michael, On 10/2/19 1:44 AM, Michael Roth wrote: > Hi everyone, > > The following new patches are queued for QEMU stable v4.0.1: > > https://github.com/mdroth/qemu/commits/stable-4.0-staging > > The release is planned for 2019-10-17: > > https://wiki.qemu.org/Planning/4.0 > > Please respond here or CC qemu-stable@nongnu.org on any patches you > think should be included in the release. Since it is a "release", these probably fit: commit 45c61c6c23918e3b05ed9ecac5b2328ebae5f774 Author: Michael Roth <mdroth@linux.vnet.ibm.com> Date: Thu Sep 12 18:12:01 2019 -0500 make-release: pull in edk2 submodules so we can build it from tarballs commit f3e330e3c319160ac04954399b5a10afc965098c Author: Michael Roth <mdroth@linux.vnet.ibm.com> Date: Thu Sep 12 18:12:02 2019 -0500 roms/Makefile.edk2: don't pull in submodules when building from tarball When is the next qemu-stable release scheduled? Do we care about Python2 use for this one?
Quoting Philippe Mathieu-Daudé (2019-10-08 08:04:52) > Hi Michael, > > On 10/2/19 1:44 AM, Michael Roth wrote: > > Hi everyone, > > > > The following new patches are queued for QEMU stable v4.0.1: > > > > https://github.com/mdroth/qemu/commits/stable-4.0-staging > > > > The release is planned for 2019-10-17: > > > > https://wiki.qemu.org/Planning/4.0 > > > > Please respond here or CC qemu-stable@nongnu.org on any patches you > > think should be included in the release. > > Since it is a "release", these probably fit: > > commit 45c61c6c23918e3b05ed9ecac5b2328ebae5f774 > Author: Michael Roth <mdroth@linux.vnet.ibm.com> > Date: Thu Sep 12 18:12:01 2019 -0500 > > make-release: pull in edk2 submodules so we can build it from tarballs > > commit f3e330e3c319160ac04954399b5a10afc965098c > Author: Michael Roth <mdroth@linux.vnet.ibm.com> > Date: Thu Sep 12 18:12:02 2019 -0500 > > roms/Makefile.edk2: don't pull in submodules when building from tarball > > When is the next qemu-stable release scheduled? Do we care about Python2 > use for this one? 4.1.1, likely early November during 4.2 hard-freeze. I think Python2 is okay since presumably downstreams would've crossed that bridge with 4.1.0, assuming you're thinking of the changes in your recent edk2 pull.
On 10/9/19 4:17 PM, Michael Roth wrote: > Quoting Philippe Mathieu-Daudé (2019-10-08 08:04:52) >> Hi Michael, >> >> On 10/2/19 1:44 AM, Michael Roth wrote: >>> Hi everyone, >>> >>> The following new patches are queued for QEMU stable v4.0.1: >>> >>> https://github.com/mdroth/qemu/commits/stable-4.0-staging >>> >>> The release is planned for 2019-10-17: >>> >>> https://wiki.qemu.org/Planning/4.0 >>> >>> Please respond here or CC qemu-stable@nongnu.org on any patches you >>> think should be included in the release. >> >> Since it is a "release", these probably fit: >> >> commit 45c61c6c23918e3b05ed9ecac5b2328ebae5f774 >> Author: Michael Roth <mdroth@linux.vnet.ibm.com> >> Date: Thu Sep 12 18:12:01 2019 -0500 >> >> make-release: pull in edk2 submodules so we can build it from tarballs >> >> commit f3e330e3c319160ac04954399b5a10afc965098c >> Author: Michael Roth <mdroth@linux.vnet.ibm.com> >> Date: Thu Sep 12 18:12:02 2019 -0500 >> >> roms/Makefile.edk2: don't pull in submodules when building from tarball >> >> When is the next qemu-stable release scheduled? Do we care about Python2 >> use for this one? > > 4.1.1, likely early November during 4.2 hard-freeze. I think Python2 is okay > since presumably downstreams would've crossed that bridge with 4.1.0, assuming > you're thinking of the changes in your recent edk2 pull. Yes. Do you mind adding these dates to https://wiki.qemu.org/Planning/4.1? Thanks, Phil.
On Tue, Oct 01, 2019 at 06:44:39PM -0500, Michael Roth wrote: > Hi everyone, Hi Michael, > Please respond here or CC qemu-stable@nongnu.org on any patches you > think should be included in the release. [...] > Anthony PERARD (1): > xen-bus: Fix backend state transition on device reset Could you cherry-pick df6180bb56cd03949c2c64083da58755fed81a61 "xen-bus: check whether the frontend is active during device reset..." as well, to fix the fix? Thanks,
Quoting Philippe Mathieu-Daudé (2019-10-09 09:23:22) > On 10/9/19 4:17 PM, Michael Roth wrote: > > Quoting Philippe Mathieu-Daudé (2019-10-08 08:04:52) > >> Hi Michael, > >> > >> On 10/2/19 1:44 AM, Michael Roth wrote: > >>> Hi everyone, > >>> > >>> The following new patches are queued for QEMU stable v4.0.1: > >>> > >>> https://github.com/mdroth/qemu/commits/stable-4.0-staging > >>> > >>> The release is planned for 2019-10-17: > >>> > >>> https://wiki.qemu.org/Planning/4.0 > >>> > >>> Please respond here or CC qemu-stable@nongnu.org on any patches you > >>> think should be included in the release. > >> > >> Since it is a "release", these probably fit: > >> > >> commit 45c61c6c23918e3b05ed9ecac5b2328ebae5f774 > >> Author: Michael Roth <mdroth@linux.vnet.ibm.com> > >> Date: Thu Sep 12 18:12:01 2019 -0500 > >> > >> make-release: pull in edk2 submodules so we can build it from tarballs > >> > >> commit f3e330e3c319160ac04954399b5a10afc965098c > >> Author: Michael Roth <mdroth@linux.vnet.ibm.com> > >> Date: Thu Sep 12 18:12:02 2019 -0500 > >> > >> roms/Makefile.edk2: don't pull in submodules when building from tarball > >> > >> When is the next qemu-stable release scheduled? Do we care about Python2 > >> use for this one? > > > > 4.1.1, likely early November during 4.2 hard-freeze. I think Python2 is okay > > since presumably downstreams would've crossed that bridge with 4.1.0, assuming > > you're thinking of the changes in your recent edk2 pull. > > Yes. > > Do you mind adding these dates to https://wiki.qemu.org/Planning/4.1? Sure, I've set the freeze date for November 18th, and the release for the 21st. > > Thanks, > > Phil. >