From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix tailq init for uio/vfio resources
Date: Thu, 12 Mar 2015 08:36:22 +0100 [thread overview]
Message-ID: <1485430.lunJJ757N3@xps13> (raw)
In-Reply-To: <1426094723-18766-1-git-send-email-david.marchand@6wind.com>
2015-03-11 18:25, David Marchand:
> Commit a2348166ea18 ("tailq: move to dynamic tailq") introduced a bug in
> uio/vfio resources list init.
>
> These resources list were pointed at through a pointer initialised only once but
> too early in the eal init (before tailqs init).
>
> Fix this by "resolving" this pointer when used (which is well after tailqs
> init).
>
> Fixes: a2348166ea18 ("tailq: move to dynamic tailq")
> Reported-by: Marvin Liu <yong.liu@intel.com>
> Reported-by: Tetsuya Mukawa <mukawa@igel.co.jp>
> Signed-off-by: David Marchand <david.marchand@6wind.com>
> ---
>
> This patch is an alternative to the patch proposed by Marvin.
> It has been tested only on Linux and with uio driver.
Applied, thanks
prev parent reply other threads:[~2015-03-12 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 17:25 David Marchand
2015-03-12 7:36 ` Thomas Monjalon [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=1485430.lunJJ757N3@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.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).