DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: wangyunjian <wangyunjian@huawei.com>, dev@dpdk.org
Cc: keith.wiles@intel.com, jerry.lilijun@huawei.com,
	xudingke@huawei.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 5/5] net/tap: fix netlink socket file descriptor check before close
Date: Tue, 7 Apr 2020 16:35:34 +0100	[thread overview]
Message-ID: <7b9013ef-6b0b-1179-724b-489fab3ec94d@intel.com> (raw)
In-Reply-To: <1586233414-7644-1-git-send-email-wangyunjian@huawei.com>

On 4/7/2020 5:23 AM, wangyunjian wrote:
> From: Yunjian Wang <wangyunjian@huawei.com>
> 
> The "internals->nlsk_fd" is possibly a zero value. Error comparison
> should check for negative fd.
> 
> Fixes: de96fe68ae95 ("net/tap: add basic flow API patterns and actions")
> CC: stable@dpdk.org
> 
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> ---
>  drivers/net/tap/rte_eth_tap.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
> index 88cd615e0..ff149342b 100644
> --- a/drivers/net/tap/rte_eth_tap.c
> +++ b/drivers/net/tap/rte_eth_tap.c
> @@ -2442,7 +2442,7 @@ rte_pmd_tap_remove(struct rte_vdev_device *dev)
>  	TAP_LOG(DEBUG, "Closing %s Ethernet device on numa %u",
>  		tuntap_types[internals->type], rte_socket_id());
>  
> -	if (internals->nlsk_fd) {
> +	if (internals->nlsk_fd >= 0) {

I guess it is unlikely socket() will return 0 as fd, but technically it seems
possible.

'tap_nl_init()' either returns '-1' for error or a valid fd, and this has been
checked as "pmd->nlsk_fd == -1" in other locations, what about doing similar here:

"if (internals->nlsk_fd != -1)"

>  		tap_flow_flush(eth_dev, NULL);
>  		tap_flow_implicit_flush(internals, NULL);
>  		tap_nl_final(internals->nlsk_fd);
> 


  reply	other threads:[~2020-04-07 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07  4:23 wangyunjian
2020-04-07 15:35 ` Ferruh Yigit [this message]
2020-04-08  0:55   ` wangyunjian

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=7b9013ef-6b0b-1179-724b-489fab3ec94d@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerry.lilijun@huawei.com \
    --cc=keith.wiles@intel.com \
    --cc=stable@dpdk.org \
    --cc=wangyunjian@huawei.com \
    --cc=xudingke@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).