DPDK announcements
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: "announce@dpdk.org" <announce@dpdk.org>
Subject: [dpdk-announce] DPDK 16.11.10 released
Date: Tue, 12 Nov 2019 15:02:42 +0000	[thread overview]
Message-ID: <05c7d904532571616d687cde411311709978b14f.camel@debian.org> (raw)

Hi all,

Here is a new stable release:
	https://fast.dpdk.org/rel/dpdk-16.11.10.tar.xz

The git tree is at:
	https://dpdk.org/browse/dpdk-stable/?h=16.11

This stable release fixes CVE-2019-14818, all users of the vhost
library are strongly encouraged to upgrade as soon as possible.

Tested with two testpmd instances, one with Vhost PMD, the other with
Virtio-user PMD. Intialization goes well, and packets flow.

Luca Boccassi

---
 doc/guides/rel_notes/release_16_11.rst      |  25 ++++++++
 lib/librte_eal/common/include/rte_version.h |   2 +-
 lib/librte_vhost/socket.c                   |  22 +++++--
 lib/librte_vhost/vhost_user.c               | 115
++++++++++++++++++++++++++++-
 lib/librte_vhost/vhost_user.h               |  4 +-
 pkg/dpdk.spec                               |  2 +-
 6 files changed, 139 insertions(+), 10 deletions(-)
Luca Boccassi (1):
      version: 16.11.10

Maxime Coquelin (3):
      vhost: add number of fds to vhost-user messages
      vhost: fix possible denial of service on SET_VRING_NUM
      vhost: fix possible denial of service by leaking FDs

Stefan Hajnoczi (1):
      vhost: validate virtqueue size

-- 
Kind regards,
Luca Boccassi

"That is not dead which can eternal lie (with security bugs). And with
strange aeons even EOL may die."

                 reply	other threads:[~2019-11-12 15:02 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=05c7d904532571616d687cde411311709978b14f.camel@debian.org \
    --to=bluca@debian.org \
    --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).