From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/6] Fix vhost security issues
Date: Mon, 18 May 2020 16:18:24 +0200 [thread overview]
Message-ID: <CAJFAV8zW7U+3iDrQFD41UcXpREcZ3BYJpyGfhVS+S2=guP6uMQ@mail.gmail.com> (raw)
In-Reply-To: <20200518131704.715877-1-ferruh.yigit@intel.com>
On Mon, May 18, 2020 at 3:17 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
>
> Marvin Liu (1):
> vhost: fix translated address not checked
>
> Maxime Coquelin (3):
> vhost: check log mmap offset and size overflow
> vhost: fix vring index check
> vhost/crypto: validate keys lengths
>
> Xiaolong Ye (1):
> vhost: fix potential memory space leak
>
> Xuan Ding (1):
> vhost: fix potential fd leak
>
> lib/librte_vhost/vhost_crypto.c | 17 +++++++++++++++++
> lib/librte_vhost/vhost_user.c | 30 +++++++++++++++++++++++-------
> lib/librte_vhost/virtio_net.c | 4 ++++
> 3 files changed, 44 insertions(+), 7 deletions(-)
>
Series applied, thanks.
--
David Marchand
prev parent reply other threads:[~2020-05-18 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 13:16 Ferruh Yigit
2020-05-18 13:16 ` [dpdk-dev] [PATCH 1/6] vhost: check log mmap offset and size overflow Ferruh Yigit
2020-05-18 13:17 ` [dpdk-dev] [PATCH 2/6] vhost: fix vring index check Ferruh Yigit
2020-05-18 13:17 ` [dpdk-dev] [PATCH 3/6] vhost/crypto: validate keys lengths Ferruh Yigit
2020-05-18 13:17 ` [dpdk-dev] [PATCH 4/6] vhost: fix translated address not checked Ferruh Yigit
2020-05-18 13:17 ` [dpdk-dev] [PATCH 5/6] vhost: fix potential memory space leak Ferruh Yigit
2020-05-18 13:17 ` [dpdk-dev] [PATCH 6/6] vhost: fix potential fd leak Ferruh Yigit
2020-05-18 14:18 ` David Marchand [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='CAJFAV8zW7U+3iDrQFD41UcXpREcZ3BYJpyGfhVS+S2=guP6uMQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=maxime.coquelin@redhat.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).