qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Stefan Weil" <sw@weilnetz.de>,
	"Jason Wang" <jasowang@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v3 0/2] net: tap: check file descriptor can be used
Date: Mon, 6 Jul 2020 10:21:53 +0200	[thread overview]
Message-ID: <616434f5-d2f7-7858-1c34-bbaaf7a036bf@redhat.com> (raw)
In-Reply-To: <20200701193951.36248-1-lvivier@redhat.com>

Hi,

ping.

I think it would be good to have this fix in next release.

Thanks,
Laurent

On 01/07/2020 21:39, Laurent Vivier wrote:
> v3: move qemu_fd_is_valid() checking into a new function
>     qemu_try_set_nonblock(), and use qemu_try_set_nonblock() in
>     qemu_set_nonblock().
> 
> v2: Add patch from Daniel to check the fd can be used
> 
>     I have updated Daniel's patch not to check for EINVAL on TUNGETIFF
>     as I think we can avoid this special case because TUNGETIFF
>     is available since kernel v2.6.27 (October 2008)
>     Moreover I think the code was wrong as it was checking with -EINVAL and
>     not EINVAL.
> 
> Daniel P. Berrang�� (1):
>   net: detect errors from probing vnet hdr flag for TAP devices
> 
> Laurent Vivier (1):
>   net: tap: check if the file descriptor is valid before using it
> 
>  include/qemu/sockets.h |  1 +
>  net/tap-bsd.c          |  2 +-
>  net/tap-linux.c        |  8 +++---
>  net/tap-solaris.c      |  2 +-
>  net/tap-stub.c         |  2 +-
>  net/tap.c              | 41 ++++++++++++++++++++++++------
>  net/tap_int.h          |  2 +-
>  util/oslib-posix.c     | 26 +++++++++++++------
>  util/oslib-win32.c     | 57 ++++++++++++++++++++++++------------------
>  9 files changed, 93 insertions(+), 48 deletions(-)
> 



      parent reply	other threads:[~2020-07-06  8:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01 19:39 [PATCH v3 0/2] net: tap: check file descriptor can be used Laurent Vivier
2020-07-01 19:39 ` [PATCH v3 1/2] net: tap: check if the file descriptor is valid before using it Laurent Vivier
2020-07-02  8:00   ` Philippe Mathieu-Daudé
2020-07-02  8:17     ` Laurent Vivier
2020-07-02  8:18       ` Philippe Mathieu-Daudé
2020-07-06  8:45         ` Philippe Mathieu-Daudé
2020-07-07  7:56   ` Jason Wang
2020-07-07 10:21     ` Laurent Vivier
2020-07-01 19:39 ` [PATCH v3 2/2] net: detect errors from probing vnet hdr flag for TAP devices Laurent Vivier
2020-07-06  8:47   ` Philippe Mathieu-Daudé
2020-07-06  8:21 ` Laurent Vivier [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=616434f5-d2f7-7858-1c34-bbaaf7a036bf@redhat.com \
    --to=lvivier@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).