From: luca.boccassi@gmail.com
To: announce@dpdk.org
Subject: [dpdk-announce] DPDK 17.11.2 released
Date: Mon, 23 Apr 2018 16:54:46 +0100 [thread overview]
Message-ID: <20180423155446.13829-1-luca.boccassi@gmail.com> (raw)
Hi all,
Here is a new stable release:
http://fast.dpdk.org/rel/dpdk-17.11.2.tar.xz
The git tree is at:
http://dpdk.org/browse/dpdk-stable/
This stable release fixes CVE-2018-1059, all users of the vhost library
are strongly encouraged to upgrade as soon as possible.
Know issues: compilation with VHOST_DEBUG is currently broken, will be
fixed in a followup release.
Luca Boccassi
---
doc/guides/rel_notes/release_17_11.rst | 15 ++
examples/vhost/virtio_net.c | 94 ++++++++++--
examples/vhost_scsi/vhost_scsi.c | 56 ++++++--
lib/librte_eal/common/include/rte_version.h | 2 +-
lib/librte_vhost/rte_vhost.h | 46 ++++++
lib/librte_vhost/rte_vhost_version.map | 6 +
lib/librte_vhost/vhost.c | 39 ++---
lib/librte_vhost/vhost.h | 8 +-
lib/librte_vhost/vhost_user.c | 58 +++++---
lib/librte_vhost/virtio_net.c | 411 ++++++++++++++++++++++++++++++++++++++++++++++-------
pkg/dpdk.spec | 2 +-
11 files changed, 619 insertions(+), 118 deletions(-)
Luca Boccassi (1):
version: 17.11.2
Maxime Coquelin (11):
vhost: fix indirect descriptors table translation size (fixes CVE-2018-1059)
vhost: check all range is mapped when translating GPAs (fixes CVE-2018-1059)
vhost: introduce safe API for GPA translation (fixes CVE-2018-1059)
vhost: ensure all range is mapped when translating QVAs (fixes CVE-2018-1059)
vhost: add support for non-contiguous indirect descs tables (fixes CVE-2018-1059)
vhost: handle virtually non-contiguous buffers in Tx (fixes CVE-2018-1059)
vhost: handle virtually non-contiguous buffers in Rx (fixes CVE-2018-1059)
vhost: handle virtually non-contiguous buffers in Rx-mrg (fixes CVE-2018-1059)
examples/vhost: move to safe GPA translation API
examples/vhost_scsi: move to safe GPA translation API
vhost: deprecate unsafe GPA translation API (fixes CVE-2018-1059)
reply other threads:[~2018-04-23 15:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180423155446.13829-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=announce@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).