patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Remy Horton <remy.horton@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	dev@dpdk.org, yliu@fridaylinux.org, jfreiman@redhat.com,
	tiwei.bie@intel.com
Cc: mst@redhat.com, vkaplans@redhat.com, jasowang@redhat.com,
	stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 15/21] vhost: don't dereference invalid dev pointer after its reallocation
Date: Mon, 4 Sep 2017 14:58:05 +0100	[thread overview]
Message-ID: <cd898068-ab7a-48a0-aa9b-15b1dd7dfc4d@intel.com> (raw)
In-Reply-To: <20170831095023.21037-16-maxime.coquelin@redhat.com>



On 31/08/2017 10:50, Maxime Coquelin wrote:
[..]
> Problem is that vhost_user_msg_handler() still derenferences old
> pointer afterward.

Spelling.. :)

Code itself looks OK.

      reply	other threads:[~2017-09-04 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170831095023.21037-1-maxime.coquelin@redhat.com>
2017-08-31  9:50 ` [dpdk-stable] " Maxime Coquelin
2017-09-04 13:58   ` Remy Horton [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=cd898068-ab7a-48a0-aa9b-15b1dd7dfc4d@intel.com \
    --to=remy.horton@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasowang@redhat.com \
    --cc=jfreiman@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mst@redhat.com \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=vkaplans@redhat.com \
    --cc=yliu@fridaylinux.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).