From: Flavio Leitner <fbl@sysclose.org>
To: Tetsuya Mukawa <mukawa@igel.co.jp>
Cc: dev@dpdk.org, ann.zhuangyanying@huawei.com
Subject: Re: [PATCH v3] vhost: Fix wrong handling of virtqueue array index
Date: Thu, 29 Oct 2015 20:18:21 -0200 [thread overview]
Message-ID: <20151029221821.GB22230@x240.home> (raw)
In-Reply-To: <1446004060-29198-1-git-send-email-mukawa@igel.co.jp>
On Wed, Oct 28, 2015 at 12:47:40PM +0900, Tetsuya Mukawa wrote:
> The patch fixes wrong handling of virtqueue array index when
> GET_VRING_BASE message comes.
>
> Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp>
> ---
vhost-user segfaults without this patch with MQ enabled.
LGTM
Acked-by: Flavio Leitner <fbl@sysclose.org>
next prev parent reply other threads:[~2015-10-29 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 3:47 [PATCH v3] vhost: Fix wrong handling of virtqueue array index Tetsuya Mukawa
2015-10-28 5:29 ` Xie, Huawei
2015-10-29 22:18 ` Flavio Leitner [this message]
2015-10-30 14:48 ` Thomas Monjalon
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=20151029221821.GB22230@x240.home \
--to=fbl@sysclose.org \
--cc=ann.zhuangyanying@huawei.com \
--cc=dev@dpdk.org \
--cc=mukawa@igel.co.jp \
/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).