From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/7] pc, pci, virtio: fixes for rc3
Date: Tue, 5 Dec 2017 02:56:41 +0200 [thread overview]
Message-ID: <20171204161112-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAFEAcA_yWQqGAzDuaPZo9vgwVywq9QazToVy7CYncVvSfhxDKw@mail.gmail.com>
On Mon, Dec 04, 2017 at 10:16:08AM +0000, Peter Maydell wrote:
> On 3 December 2017 at 04:56, Michael S. Tsirkin <mst@redhat.com> wrote:
> > On Fri, Dec 01, 2017 at 06:05:25PM +0000, Peter Maydell wrote:
> >> On 1 December 2017 at 17:08, Michael S. Tsirkin <mst@redhat.com> wrote:
> >> > Chao Gao (1):
> >> > i386/msi: Correct mask of destination ID in MSI address
> >> >
> >> > Greg Kurz (1):
> >> > vhost: fix error check in vhost_verify_ring_mappings()
> >> >
> >> > Igor Mammedov (1):
> >> > pc: fix crash on attempted cpu unplug
> >> >
> >> > Marc-André Lureau (1):
> >> > dump-guest-memory.py: fix No symbol "vmcoreinfo_find"
> >> >
> >> > Maxime Coquelin (2):
> >> > virtio: Add queue interface to restore avail index from vring used index
> >> > vhost: restore avail index from vring used index on disconnection
> >> >
> >> > Prasad J Pandit (1):
> >> > virtio: check VirtQueue Vring object is set
> >>
> >> Are any of these so important that we would absolutely refuse
> >> to release without the fixes (ie they justify rolling an rc4
> >> that we would otherwise not have needed) ?
>
> > The msi one is less important it just happened to be queued a while ago
> > and I didn't want to rebase all testing. Others are crashers but they
> > don't affect everyone. So I wouldn't be sure, but there's also a
> > security fix in there, so yes, I suspect we are better off with rc4, and
> > if we do I think including others is justified (except maybe the msi
> > one, if you feel strongly I'll rebase and drop it).
>
> The bar has to be set quite high here, because if it turns out
> that there are problems with a bug fix then we are out of time
> to rework or revert it. And the more fixes we throw in at the
> last minute, even if they're individually simple, the more
> likely that one of them turns out to have unexpected consequences.
>
> So: were any of these bugs present in the 2.10 release? If so,
> that strongly argues for not trying to fix them at this point.
>
> With all of these patches plus David Gibson's, that would be
> 10 new patches in rc4. That is definitely more than would be
> ideal.
>
> thanks
> -- PMM
None of these are regressions. Except for the msix one, they
do fix major bugs for features new in this release though.
I'll resend it without msix, pls go ahead and ignore if
you think a .1 stable release is a better place to put them.
--
MST
prev parent reply other threads:[~2017-12-05 0:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 17:08 [Qemu-devel] [PULL 0/7] pc, pci, virtio: fixes for rc3 Michael S. Tsirkin
2017-12-01 17:08 ` [Qemu-devel] [PULL 1/7] i386/msi: Correct mask of destination ID in MSI address Michael S. Tsirkin
2017-12-01 17:08 ` [Qemu-devel] [PULL 2/7] virtio: Add queue interface to restore avail index from vring used index Michael S. Tsirkin
2017-12-01 17:08 ` [Qemu-devel] [PULL 3/7] vhost: restore avail index from vring used index on disconnection Michael S. Tsirkin
2017-12-01 17:08 ` [Qemu-devel] [PULL 4/7] dump-guest-memory.py: fix No symbol "vmcoreinfo_find" Michael S. Tsirkin
2017-12-01 17:08 ` [Qemu-devel] [PULL 5/7] vhost: fix error check in vhost_verify_ring_mappings() Michael S. Tsirkin
2017-12-01 17:08 ` [Qemu-devel] [PULL 6/7] virtio: check VirtQueue Vring object is set Michael S. Tsirkin
2017-12-01 17:09 ` [Qemu-devel] [PULL 7/7] pc: fix crash on attempted cpu unplug Michael S. Tsirkin
2017-12-01 18:05 ` [Qemu-devel] [PULL 0/7] pc, pci, virtio: fixes for rc3 Peter Maydell
2017-12-03 4:56 ` Michael S. Tsirkin
2017-12-04 10:16 ` Peter Maydell
2017-12-04 17:18 ` Peter Maydell
2017-12-05 0:56 ` Michael S. Tsirkin [this message]
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=20171204161112-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).