patches for DPDK stable branches
 help / color / mirror / Atom feed
From: wangyunjian <wangyunjian@huawei.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
	"zhihong.wang@intel.com" <zhihong.wang@intel.com>,
	xudingke <xudingke@huawei.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] net/virtio-user: fix return value of tap offload sets not checked
Date: Mon, 13 Jan 2020 07:26:20 +0000	[thread overview]
Message-ID: <34EFBCA9F01B0748BEB6B629CE643AE60CE22606@dggemm513-mbx.china.huawei.com> (raw)
In-Reply-To: <20200113021605.GA84114@___>

> -----Original Message-----
> From: Tiwei Bie [mailto:tiwei.bie@intel.com]
> Sent: Monday, January 13, 2020 10:16 AM
> To: wangyunjian <wangyunjian@huawei.com>
> Cc: dev@dpdk.org; maxime.coquelin@redhat.com; zhihong.wang@intel.com;
> xudingke <xudingke@huawei.com>; stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] net/virtio-user: fix return value of tap offload
> sets not checked
> 
> On Thu, Jan 09, 2020 at 08:18:24PM +0800, Yunjian Wang wrote:
> > The function vhost_kernel_tap_set_offload() could return errors, the
> > return value need to be checked. And there is no need to fail when
> > error is -ENOTSUP.
> >
> > Fixes: 1db4d2330bc8 ("net/virtio-user: check negotiated features
> > before set")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> > ---
> > v2:
> >  * No need to fail when error is -ENOTSUP.
> > ---
> >  drivers/net/virtio/virtio_user/vhost_kernel_tap.c | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/virtio/virtio_user/vhost_kernel_tap.c
> > b/drivers/net/virtio/virtio_user/vhost_kernel_tap.c
> > index 76bf75423..2a0c2106d 100644
> > --- a/drivers/net/virtio/virtio_user/vhost_kernel_tap.c
> > +++ b/drivers/net/virtio/virtio_user/vhost_kernel_tap.c
> > @@ -66,6 +66,7 @@ vhost_kernel_open_tap(char **p_ifname, int hdr_size,
> int req_mq,
> >  	int sndbuf = INT_MAX;
> >  	struct ifreq ifr;
> >  	int tapfd;
> > +	int ret;
> >
> >  	/* TODO:
> >  	 * 1. verify we can get/set vnet_hdr_len, tap_probe_vnet_hdr_len @@
> > -131,7 +132,9 @@ vhost_kernel_open_tap(char **p_ifname, int hdr_size, int
> req_mq,
> >  		goto error;
> >  	}
> >
> > -	vhost_kernel_tap_set_offload(tapfd, features);
> > +	ret = vhost_kernel_tap_set_offload(tapfd, features);
> > +	if (ret < 0 && ret != ENOTSUP)
> 
> s/ENOTSUP/-ENOTSUP/

Thanks, I will fix it in v3.

Yunjian

> 
> > +		goto error;
> >
> >  	memset(&ifr, 0, sizeof(ifr));
> >  	ifr.ifr_hwaddr.sa_family = ARPHRD_ETHER;
> > --
> > 2.19.1
> >
> >

      reply	other threads:[~2020-01-13  7:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09 12:18 Yunjian Wang
2020-01-13  2:16 ` Tiwei Bie
2020-01-13  7:26   ` wangyunjian [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=34EFBCA9F01B0748BEB6B629CE643AE60CE22606@dggemm513-mbx.china.huawei.com \
    --to=wangyunjian@huawei.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=xudingke@huawei.com \
    --cc=zhihong.wang@intel.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).