patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Tiwei Bie <tiwei.bie@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: stable@dpdk.org, Zhike Wang <wangzk320@163.com>
Subject: Re: [dpdk-stable] [16.11 LTS PATCH v2] vhost: fix vring requests validation broken if no FD
Date: Fri, 15 Nov 2019 14:04:47 +0000	[thread overview]
Message-ID: <36d63ecbf14bcd2b32f5ab116a9c97ee4e56a62c.camel@debian.org> (raw)
In-Reply-To: <20191115122408.GA1432@___>

On Fri, 2019-11-15 at 20:24 +0800, Tiwei Bie wrote:
> On Fri, Nov 15, 2019 at 11:36:15AM +0100, Maxime Coquelin wrote:
> > From: Zhike Wang <
> > wangzk320@163.com
> > >
> > 
> > When VHOST_USER_VRING_NOFD_MASK is set, the fd_num is 0,
> > so validate_msg_fds() will return error. In this case,
> > the negotiation of vring message between vhost user front end and
> > back end would fail, and as a result, vhost user link could NOT be
> > up.
> > 
> > How to reproduce:
> > 1.Run dpdk testpmd insides VM, which locates at host with ovs+dpdk.
> > 2.Notice that inside ovs there are endless logs regarding failure
> > to
> > handle VHOST_USER_SET_VRING_CALL, and link of vm could NOT be up.
> > 
> > Fixes: 1bf11cfb7c7c ("vhost: fix possible denial of service by
> > leaking FDs")
> > Cc: 
> > stable@dpdk.org
> > 
> > 
> > Signed-off-by: Zhike Wang <
> > wangzk320@163.com
> > >
> > Reviewed-by: Maxime Coquelin <
> > maxime.coquelin@redhat.com
> > >
> > ---
> >  lib/librte_vhost/vhost_user.c | 13 ++++++++++---
> >  1 file changed, 10 insertions(+), 3 deletions(-)
> 
> Reviewed-by: Tiwei Bie <
> tiwei.bie@intel.com
> >
> 
> Thanks!
> Tiwei

Thanks, applied

-- 
Kind regards,
Luca Boccassi

      reply	other threads:[~2019-11-15 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 10:36 Maxime Coquelin
2019-11-15 12:24 ` Tiwei Bie
2019-11-15 14:04   ` Luca Boccassi [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=36d63ecbf14bcd2b32f5ab116a9c97ee4e56a62c.camel@debian.org \
    --to=bluca@debian.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=wangzk320@163.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).