From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: stable@dpdk.org
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-stable] [PATCH v16.11 LTS 0/6] Vhost: CVE-2018-1059 fixes
Date: Mon, 23 Apr 2018 17:59:12 +0200 [thread overview]
Message-ID: <20180423155918.21350-1-maxime.coquelin@redhat.com> (raw)
This series fixes the security vulnerability referenced
as CVE-2018-1059.
Patches are already applied to the branch, but reviews
are encouraged. Any issues spotted would be fixed on top.
Maxime Coquelin (6):
vhost: check all range is mapped when translating GPAs
vhost: ensure all range is mapped when translating QVAs
vhost: add support for non-contiguous indirect descs tables
vhost: handle virtually non-contiguous buffers in Tx
vhost: handle virtually non-contiguous buffers in Rx
vhost: handle virtually non-contiguous buffers in Rx-mrg
lib/librte_vhost/vhost.h | 19 ++-
lib/librte_vhost/vhost_user.c | 41 +++--
lib/librte_vhost/virtio_net.c | 355 +++++++++++++++++++++++++++++++++++++-----
3 files changed, 359 insertions(+), 56 deletions(-)
--
2.14.3
next reply other threads:[~2018-04-23 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 15:59 Maxime Coquelin [this message]
2018-04-23 15:59 ` [dpdk-stable] [PATCH v16.11 LTS 1/6] vhost: check all range is mapped when translating GPAs Maxime Coquelin
2018-04-23 15:59 ` [dpdk-stable] [PATCH v16.11 LTS 2/6] vhost: ensure all range is mapped when translating QVAs Maxime Coquelin
2018-04-23 15:59 ` [dpdk-stable] [PATCH v16.11 LTS 3/6] vhost: add support for non-contiguous indirect descs tables Maxime Coquelin
2018-04-23 15:59 ` [dpdk-stable] [PATCH v16.11 LTS 4/6] vhost: handle virtually non-contiguous buffers in Tx Maxime Coquelin
2018-04-23 15:59 ` [dpdk-stable] [PATCH v16.11 LTS 5/6] vhost: handle virtually non-contiguous buffers in Rx Maxime Coquelin
2018-04-23 15:59 ` [dpdk-stable] [PATCH v16.11 LTS 6/6] vhost: handle virtually non-contiguous buffers in Rx-mrg 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=20180423155918.21350-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=stable@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).