From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, david.marchand@redhat.com, chenbo.xia@intel.com
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [PATCH v3 0/2] Vhost: fix FD leaks and improve logs
Date: Tue, 7 Feb 2023 17:22:38 +0100 [thread overview]
Message-ID: <20230207162240.292020-1-maxime.coquelin@redhat.com> (raw)
This two-patches series fix possible FD leaks when
receiving Vhost-user messages fails. It also improve
logging by differentiating message's buffer truncation
and control data truncation.
Changes in v3:
==============
- Improve logs on error (David)
Maxime Coquelin (2):
vhost: fix possible FDs leak
vhost: fix possible FD leaks on truncation
lib/vhost/socket.c | 8 +++++---
lib/vhost/vhost_user.c | 40 ++++++++++++++++++++++++++--------------
2 files changed, 31 insertions(+), 17 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-07 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 16:22 Maxime Coquelin [this message]
2023-02-07 16:22 ` [PATCH v3 1/2] vhost: fix possible FDs leak Maxime Coquelin
2023-02-07 16:22 ` [PATCH v3 2/2] vhost: fix possible FD leaks on truncation Maxime Coquelin
2023-02-09 12:13 ` [PATCH v3 0/2] Vhost: fix FD leaks and improve logs 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=20230207162240.292020-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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).