Thread (8 messages) 8 messages, 4 authors, 2012-11-01

RE: [PATCH] lockd: fix races in per-net NSM client handling

From: Myklebust, Trond <hidden>
Date: 2012-10-31 18:18:54
Also in: lkml

-----Original Message-----
From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
owner@vger.kernel.org] On Behalf Of Pawel Sikora
Sent: Wednesday, October 31, 2012 2:03 PM
To: Greg KH
Cc: skinsbursky@parallels.com; stable@vger.kernel.org; linux-
kernel@vger.kernel.org; baggins@pld-linux.org; arekm@pld-linux.org
Subject: Re: [PATCH] lockd: fix races in per-net NSM client handling

On Wednesday 31 of October 2012 10:49:46 Greg KH wrote:
quoted
On Wed, Oct 31, 2012 at 06:27:36PM +0100, Paweł Sikora wrote:
quoted
Hi,

the patch metioned in https://lkml.org/lkml/2012/10/24/175 seems to
fix the 3.6.3 oops (while 3.6.2 works fine) at 16-cores opteron server.
please queue this path for 3.6.$next.
Is it in Linus's tree already?  If so, what is the git commit id?
the mainstream contains some lock deamon fixes already:

* e498daa LOCKD: Clear ln->nsm_clnt only when ln->nsm_users is zero
* a4ee8d9 LOCKD: fix races in nsm_client_get

but i don't know where is the right fix. Stanislav, could you put some light on
this?
The above 2 patches (which are already in 3.6.5) replace Stanislav's patch, which will not be merged upstream.

Trond
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help