DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost_user: Make sure that memory map is set before attempting address translation
Date: Wed, 13 Jan 2016 09:38:10 +0800	[thread overview]
Message-ID: <20160113013810.GD19531@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1452609306-7724-1-git-send-email-p.fedin@samsung.com>

On Tue, Jan 12, 2016 at 05:35:06PM +0300, Pavel Fedin wrote:
> Malfunctioning virtio clients may not send VHOST_USER_SET_MEM_TABLE for
> some reason. This causes NULL dereference in qva_to_vva().
> 
> Change-Id: Ibc8f6637fb5fb9885b02c316adf18afd45e0d49a

What's this? An internal track id? If so, you should not include it
here: it's just meaningless to us.

Otherwise, this patch looks good to me.

	--yliu

  reply	other threads:[~2016-01-13  1:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 14:35 Pavel Fedin
2016-01-13  1:38 ` Yuanhan Liu [this message]
2016-01-13  7:18   ` Pavel Fedin
2016-01-13  7:24     ` Yuanhan Liu

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=20160113013810.GD19531@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=dev@dpdk.org \
    --cc=p.fedin@samsung.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).