From: Jason Wang <jasowang@redhat.com>
To: Jay Zhou <jianjay.zhou@huawei.com>, qemu-devel@nongnu.org
Cc: mst@redhat.com, imammedo@redhat.com, weidong.huang@huawei.com,
wangxinxin.wang@huawei.com, arei.gonglei@huawei.com
Subject: Re: [Qemu-devel] [PATCH] tap: close fd conditionally when error occured
Date: Mon, 15 Jan 2018 15:21:06 +0800 [thread overview]
Message-ID: <2ec90e7e-0625-62c7-a5a8-3a8aee68114f@redhat.com> (raw)
In-Reply-To: <1515742232-49096-1-git-send-email-jianjay.zhou@huawei.com>
On 2018年01月12日 15:30, Jay Zhou wrote:
> If netdev_add tap,id=net0,vhost=on failed in net_init_tap_one(),
> the followed up device_add virtio-net-pci,netdev=net0 will fail
> too, prints:
>
> TUNSETOFFLOAD ioctl() failed: Bad file descriptor TUNSETOFFLOAD
> ioctl() failed: Bad file descriptor
>
> The reason is that the fd of tap is closed when error occured after
> calling net_init_tap_one().
>
> I think the fd should be closed in these two case:
> 1.tap_set_sndbuf() failed
> 2.tap_set_sndbuf() succeeded but vhost failed to initialize with
> vhostforce flag on
> Meanwhile, the fd should not be closed just because vhost failed to
> initialize but without vhostforce flag. So the followed up device_add
> can fall back to userspace virtio successfully.
>
> Suggested-by: Michael S. Tsirkin <mst@redhat.com>
> Suggested-by: Igor Mammedov <imammedo@redhat.com>
> Suggested-by: Jason Wang <jasowang@redhat.com>
> Signed-off-by: Jay Zhou <jianjay.zhou@huawei.com>
> ---
> net/tap.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/net/tap.c b/net/tap.c
> index 979e622..3ed72eb 100644
> --- a/net/tap.c
> +++ b/net/tap.c
> @@ -651,6 +651,9 @@ static void net_init_tap_one(const NetdevTapOptions *tap, NetClientState *peer,
> tap_set_sndbuf(s->fd, tap, &err);
> if (err) {
> error_propagate(errp, err);
> + if (!tap->has_fd && !tap->has_fds) {
> + close(fd);
> + }
> return;
> }
>
> @@ -687,14 +690,14 @@ static void net_init_tap_one(const NetdevTapOptions *tap, NetClientState *peer,
> vhostfd = monitor_fd_param(cur_mon, vhostfdname, &err);
> if (vhostfd == -1) {
> error_propagate(errp, err);
> - return;
> + goto cleanup;
> }
> } else {
> vhostfd = open("/dev/vhost-net", O_RDWR);
> if (vhostfd < 0) {
> error_setg_errno(errp, errno,
> "tap: open vhost char device failed");
> - return;
> + goto cleanup;
> }
> fcntl(vhostfd, F_SETFL, O_NONBLOCK);
> }
> @@ -704,11 +707,18 @@ static void net_init_tap_one(const NetdevTapOptions *tap, NetClientState *peer,
> if (!s->vhost_net) {
> error_setg(errp,
> "vhost-net requested but could not be initialized");
So error_setg() is not appropriate here consider it was not trated as an
error. We probably just need some warning.
> - return;
> + goto cleanup;
> }
> } else if (vhostfdname) {
> error_setg(errp, "vhostfd(s)= is not valid without vhost");
> }
> +
> +cleanup:
> + if (!tap->has_fd && !tap->has_fds && tap->has_vhostforce &&
> + tap->vhostforce) {
> + close(fd);
I would still let caller to decide whether or not to close the fd.
Thanks
> + }
> + return;
> }
>
> static int get_fds(char *str, char *fds[], int max)
> @@ -877,7 +887,6 @@ free_fail:
> vnet_hdr, fd, &err);
> if (err) {
> error_propagate(errp, err);
> - close(fd);
> return -1;
> }
> } else {
> @@ -916,7 +925,6 @@ free_fail:
> vhostfdname, vnet_hdr, fd, &err);
> if (err) {
> error_propagate(errp, err);
> - close(fd);
> return -1;
> }
> }
next prev parent reply other threads:[~2018-01-15 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 7:30 [Qemu-devel] [PATCH] tap: close fd conditionally when error occured Jay Zhou
2018-01-15 7:21 ` Jason Wang [this message]
2018-01-15 12:55 ` Zhoujian (jay)
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=2ec90e7e-0625-62c7-a5a8-3a8aee68114f@redhat.com \
--to=jasowang@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=imammedo@redhat.com \
--cc=jianjay.zhou@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.com \
/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).