patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>, dev@dpdk.org
Cc: tiwei.bie@intel.com, zhihong.wang@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v3] vhost: fix null pointer checking
Date: Wed, 17 Apr 2019 09:54:45 +0200	[thread overview]
Message-ID: <b4a6a2af-8cd3-33e2-f899-8360b69e2464@redhat.com> (raw)
In-Reply-To: <20190411144840.19942-1-mohammad.abdul.awal@intel.com>



On 4/11/19 4:48 PM, Mohammad Abdul Awal wrote:
> Null value for parameters will cause segfault.
> 
> Fixes: d7280c9fff ("vhost: support selective datapath")
> Fixes: 72e8543093 ("vhost: add API to get MTU value")
> Fixes: a277c71598 ("vhost: refactor code structure")
> Fixes: ca33faf9ef ("vhost: introduce API to fetch negotiated features")
> Fixes: eb32247457 ("vhost: export guest memory regions")
> Fixes: 40ef286f23 ("vhost: export vhost vring info")
> Fixes: bd2e0c3fe5 ("vhost: add APIs for live migration")
> Fixes: 0b8572a0c1 ("vhost: add external message handling to the API")
> Fixes: b4953225ce ("vhost: add APIs for datapath configuration")
> Fixes: 5fbb3941da ("vhost: introduce driver features related APIs")
> Fixes: 292959c719 ("vhost: cleanup unix socket")
> Cc:stable@dpdk.org
> 
> Signed-off-by: Mohammad Abdul Awal<mohammad.abdul.awal@intel.com>
> ---
> v3: fixed per review comments
> 
> v2: fixed per review comments
> 
>   lib/librte_vhost/socket.c |  8 +++++++-
>   lib/librte_vhost/vdpa.c   |  5 ++++-
>   lib/librte_vhost/vhost.c  | 16 ++++++++--------
>   3 files changed, 19 insertions(+), 10 deletions(-)


Applied to dpdk-next-virtio/master.

Thanks,
Maxime

      parent reply	other threads:[~2019-04-17  7:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 14:48 Mohammad Abdul Awal
2019-04-12  5:21 ` Tiwei Bie
2019-04-17  7:54 ` Maxime Coquelin [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=b4a6a2af-8cd3-33e2-f899-8360b69e2464@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mohammad.abdul.awal@intel.com \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=zhihong.wang@intel.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).