patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, xuan.ding@intel.com, stephen@networkplumber.org,
	thomas@monjalon.net, stable@dpdk.org, chenbo.xia@intel.com,
	xuemingl@nvidia.com
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-stable] [PATCH v4 0/3] vhost: fix fd an memory leaks
Date: Thu, 12 Nov 2020 18:10:26 +0100	[thread overview]
Message-ID: <20201112171029.354593-1-maxime.coquelin@redhat.com> (raw)

This series fixes several leaks in Vhost-user requests
handling.

Thanks to Xuan Ding from Intel for reporting these
issues.

Changes in v4:
- Fix wrong return value in set_mem_table (Xueming)

Changes in v3:
- Remove the right closing of fds. (Chenbo)
Changes in v2:
- Fix typos in commit messages. (Chenbo)
- Remove useless closing of fds in set_log_base. (Chenbo)

Maxime Coquelin (3):
  vhost: fix error path when setting memory tables
  vhost: fix fd leak in dirty logging setup
  vhost: fix fd leak in kick setup

 lib/librte_vhost/vhost_user.c | 74 +++++++++++++++++++++++------------
 1 file changed, 49 insertions(+), 25 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-11-12 17:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 17:10 Maxime Coquelin [this message]
2020-11-12 17:10 ` [dpdk-stable] [PATCH v4 1/3] vhost: fix error path when setting memory tables Maxime Coquelin
2020-11-13  7:39   ` Xueming(Steven) Li
2020-11-12 17:10 ` [dpdk-stable] [PATCH v4 2/3] vhost: fix fd leak in dirty logging setup Maxime Coquelin
2020-11-12 17:10 ` [dpdk-stable] [PATCH v4 3/3] vhost: fix fd leak in kick setup Maxime Coquelin
2020-11-13  7:41   ` Xueming(Steven) Li
2020-11-13  8:39 ` [dpdk-stable] [PATCH v4 0/3] vhost: fix fd an memory leaks Maxime Coquelin

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=20201112171029.354593-1-maxime.coquelin@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=xuan.ding@intel.com \
    --cc=xuemingl@nvidia.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).