From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
stable@dpdk.org, jianfeng.tan@intel.com
Subject: Re: [dpdk-stable] [PATCH v2 v16.11 LTS] vhost-user: fix deadlock in case of NUMA realloc
Date: Wed, 04 Apr 2018 20:55:50 +0100 [thread overview]
Message-ID: <1522871750.16877.21.camel@debian.org> (raw)
In-Reply-To: <1a0753a2-a37c-0ec8-d126-873bba2a277d@redhat.com>
On Wed, 2018-04-04 at 13:57 +0100, Kevin Traynor wrote:
> On 03/28/2018 08:51 PM, Maxime Coquelin wrote:
> > Virtqueue's access lock was recently introduced to protect
> > the device against async changes.
> >
> > One problem with the v16.11 backport is that in case of NUMA
> > reallocation, the device gets stuck because the old access_lock
> > gets unlocked instead of its reallocated copy. On the next
> > vhost-user message received, the thread keeps spinning on the
> > lock, as it will never be unlocked.
> >
>
> Reviewed-by: Kevin Traynor <ktraynor@redhat.com>
Thanks, applied&pushed to dpdk-stable/16.11
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2018-04-04 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 19:51 Maxime Coquelin
2018-04-04 12:57 ` Kevin Traynor
2018-04-04 19:55 ` Luca Boccassi [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=1522871750.16877.21.camel@debian.org \
--to=bluca@debian.org \
--cc=jianfeng.tan@intel.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@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).