From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <luca.boccassi@gmail.com>
Received: from mail-wm0-f68.google.com (mail-wm0-f68.google.com [74.125.82.68])
 by dpdk.org (Postfix) with ESMTP id 652521C708
 for <stable@dpdk.org>; Wed,  4 Apr 2018 21:55:52 +0200 (CEST)
Received: by mail-wm0-f68.google.com with SMTP id r131so325270wmb.2
 for <stable@dpdk.org>; Wed, 04 Apr 2018 12:55:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to
 :references:content-transfer-encoding:mime-version;
 bh=9+0B5IT5yHDB71UKR/bDKwcwB43C/pbNudSDT8+NjmU=;
 b=h3mxF6cCX/m+rUPDlSSls1/k4fZGO0cpB+luQFU+UUh6iUnMFEMrgwViLHhSgeBNU9
 glfZtDiblin5rTgukjtKvd9kQczifKmHnCdPlSi6a/QMBwnaz1LINazbyi+uzLECthTx
 5oSqJh7gJEt58/vufRc1d3W54Cwnsu3+DvZc8XVDOUKbx07lIfK9a9fmQ6lKOB7RZtDS
 1pyZZ+pTYMOylFIeENLRy4iEPmp0Q8b6D++Iif8ApCTgsCjcSLNKpp8c+RiYbtlhgRrC
 MbokYA9/jKnDP0KElMcLknIaLwWLOa+RLZRR+6gr7FIBb0mdrKQjb05ugU1g1OkX1zhC
 QYgg==
X-Gm-Message-State: AElRT7HGP81RHZVBTbChfIconVrrbtuQIBXIsPiIuzGQsF7izJf7NBvM
 Ua6kAt72As2Pv6pP9AVjGIQ=
X-Google-Smtp-Source: AIpwx49BBB4M0js/C1jyzcsRBKh6FwrKVfOAhjcTKrWU5bbC8BfppuAF89wOjCfnykv2gY7D5ZpQsA==
X-Received: by 10.28.1.131 with SMTP id 125mr7706658wmb.96.1522871752084;
 Wed, 04 Apr 2018 12:55:52 -0700 (PDT)
Received: from localhost ([2a00:23c5:be96:5300:2cbb:c5a7:285d:355])
 by smtp.gmail.com with ESMTPSA id r15sm5256730wrr.79.2018.04.04.12.55.51
 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
 Wed, 04 Apr 2018 12:55:51 -0700 (PDT)
Message-ID: <1522871750.16877.21.camel@debian.org>
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
Date: Wed, 04 Apr 2018 20:55:50 +0100
In-Reply-To: <1a0753a2-a37c-0ec8-d126-873bba2a277d@redhat.com>
References: <20180328195135.25692-1-maxime.coquelin@redhat.com>
 <1a0753a2-a37c-0ec8-d126-873bba2a277d@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Evolution 3.22.6-1+deb9u1 
Mime-Version: 1.0
Subject: Re: [dpdk-stable] [PATCH v2 v16.11 LTS] vhost-user: fix deadlock in
 case of NUMA realloc
X-BeenThere: stable@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches for DPDK stable branches <stable.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/stable>,
 <mailto:stable-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/stable/>
List-Post: <mailto:stable@dpdk.org>
List-Help: <mailto:stable-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/stable>,
 <mailto:stable-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2018 19:55:52 -0000

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.
> >=20
> > 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.
> >=20
>=20
> Reviewed-by: Kevin Traynor <ktraynor@redhat.com>

Thanks, applied&pushed to dpdk-stable/16.11

--=20
Kind regards,
Luca Boccassi