qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Li Qiang" <liq3ea@gmail.com>, "Jason Wang" <jasowang@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>,
	QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] net: tap: use qemu_set_nonblock
Date: Wed, 21 Nov 2018 11:30:41 -0600	[thread overview]
Message-ID: <60500f8b-47e8-c530-076a-d7f14d0f0ee5@redhat.com> (raw)
In-Reply-To: <20181121072237-mutt-send-email-mst@kernel.org>

On 11/21/18 6:23 AM, Michael S. Tsirkin wrote:

>>
>> I agree it is good to preserve fcntl flags though, so this patch
>> looks desirable.
>>
>> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> 
> Sure
> 
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
> 
> but really not for this release I guess as we are in freeze.

We're in freeze, so the criteria is: Does this fix a bug that we would 
otherwise not want in 3.1.  If the code is pre-existing (that is, if 3.0 
was released with the same problem), or then delaying the patch to 4.0 
is an easier call to make.  If the problem is new to 3.1, then fixing it 
for -rc3 is still reasonable with maintainer discretion (although once 
-rc3 lands, we want as little as possible to go into -rc4, even if our 
track record says we will be unable to avoid -rc4 altogether).

I think that losing flags is likely enough to be a noticeable bug worth 
fixing for 3.1, but I did not research when the problem was introduced, 
so I don't have a strong preference for 3.1 vs. 4.0.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  parent reply	other threads:[~2018-11-21 17:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21 11:21 [Qemu-devel] [PATCH] net: tap: use qemu_set_nonblock Li Qiang
2018-11-21 11:28 ` Marc-André Lureau
2018-11-21 11:34   ` Li Qiang
2018-11-21 11:57   ` Daniel P. Berrangé
2018-11-21 12:23     ` Michael S. Tsirkin
2018-11-21 14:21       ` Markus Armbruster
2018-11-21 17:30       ` Eric Blake [this message]
2018-11-21 17:39         ` Michael S. Tsirkin
2018-11-22  2:22           ` Jason Wang
2019-03-10 11:26             ` Li Qiang
2019-03-11  9:35               ` Jason Wang

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=60500f8b-47e8-c530-076a-d7f14d0f0ee5@redhat.com \
    --to=eblake@redhat.com \
    --cc=berrange@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=liq3ea@gmail.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=mst@redhat.com \
    --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).