DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	wangyunjian <wangyunjian@huawei.com>
Cc: dev@dpdk.org, keith.wiles@intel.com, jerry.lilijun@huawei.com,
	xudingke@huawei.com
Subject: Re: [dpdk-dev] [PATCH v5 0/5] fixes for tap
Date: Thu, 16 Apr 2020 12:54:38 +0100	[thread overview]
Message-ID: <484fb161-1543-19d1-0a8e-3d2f70a33cce@intel.com> (raw)
In-Reply-To: <20200415220712.07d4f4fa@hermes.lan>

On 4/16/2020 6:07 AM, Stephen Hemminger wrote:
> On Thu, 16 Apr 2020 11:03:57 +0800
> wangyunjian <wangyunjian@huawei.com> wrote:
> 
>> From: Yunjian Wang <wangyunjian@huawei.com>
>>
>> This series include five fixes patches for tap PMD driver.
>>
>> --
>> v5:
>> * fix check fd error
>> v4:
>> * Update some code suggested by Ferruh Yigit and Stephen Hemminger
>> * Update commit log
>> * Add fix leak of fds on failure
>> v3:
>> * Add fix close a vaild fd and netlink socket file descriptor check
>>   before close
>> v2:
>> * Add null check in tap_rxq_pool_free()
>>
>> Yunjian Wang (5):
>>   net/tap: fix mbuf double free when writev fails
>>   net/tap: fix mbuf and mem leak during queue release
>>   net/tap: fix check for mbuf's nb_segs failure
>>   net/tap: fix close a valid fd
>>   net/tap: fix leak of fds on failure
>>
>>  drivers/net/tap/rte_eth_tap.c | 106 ++++++++++++++++++++--------------
>>  1 file changed, 63 insertions(+), 43 deletions(-)
>>
> 
> These all look good.
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> 

For series,
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Series applied to dpdk-next-net/master, thanks.

      parent reply	other threads:[~2020-04-16 11:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16  3:03 wangyunjian
2020-04-16  5:07 ` Stephen Hemminger
2020-04-16 11:54   ` Ferruh Yigit
2020-04-16 11:54   ` Ferruh Yigit [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=484fb161-1543-19d1-0a8e-3d2f70a33cce@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerry.lilijun@huawei.com \
    --cc=keith.wiles@intel.com \
    --cc=stephen@networkplumber.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).