From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: dev@dpdk.org
Cc: huawei.xie@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/vhost: fix corrupted vdev tailq list
Date: Mon, 13 Jun 2016 17:53:16 +0800 [thread overview]
Message-ID: <20160613095316.GQ10038@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1465270376-16560-1-git-send-email-yuanhan.liu@linux.intel.com>
On Tue, Jun 07, 2016 at 11:32:56AM +0800, Yuanhan Liu wrote:
> There are two tailq lists, one for logging all vhost devices, another
> one for logging vhost devices distributed on a specific core. However,
> there is just one tailq entry, named "next", to chain the two list,
> which is wrong and could result to a corrupted tailq list, that the
> tailq list might always be non-empty: the entry is still there even
> after you have invoked TAILQ_REMOVE several times.
>
> Fix it by introducing two tailq entries, one for each list.
>
> Fixes: 45657a5c6861 ("examples/vhost: use tailq to link vhost devices")
>
> Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Applied to dpdk-next-virtio.
--yliu
prev parent reply other threads:[~2016-06-13 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 3:32 Yuanhan Liu
2016-06-13 9:53 ` Yuanhan Liu [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=20160613095316.GQ10038@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@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).