DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yunjian Wang <wangyunjian@huawei.com>
To: <dev@dpdk.org>
Cc: <grive@u256.net>, <hkalra@marvell.com>,
	<huangshaozhang@huawei.com>,
	Yunjian Wang <wangyunjian@huawei.com>
Subject: [dpdk-dev] [PATCH 0/2] fixes for failsafe/tap
Date: Tue, 7 Jun 2022 14:49:12 +0800	[thread overview]
Message-ID: <cover.1654516650.git.wangyunjian@huawei.com> (raw)

This series include two fixes patches for failsafe/tap

Yunjian Wang (2):
  net/failsafe: fix freeing after device release
  net/tap: fix use after free on error path

 drivers/net/failsafe/failsafe.c | 2 +-
 drivers/net/tap/rte_eth_tap.c   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
2.27.0


             reply	other threads:[~2022-06-07  6:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  6:49 Yunjian Wang [this message]
2022-06-07  6:50 ` [dpdk-dev] [PATCH 1/2] net/failsafe: fix freeing after device release Yunjian Wang
2022-06-07  6:50 ` [dpdk-dev] [PATCH 2/2] net/tap: fix use after free on error path Yunjian Wang
2022-06-08 12:43 ` [dpdk-dev] [PATCH 0/2] fixes for failsafe/tap Andrew Rybchenko

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=cover.1654516650.git.wangyunjian@huawei.com \
    --to=wangyunjian@huawei.com \
    --cc=dev@dpdk.org \
    --cc=grive@u256.net \
    --cc=hkalra@marvell.com \
    --cc=huangshaozhang@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).