linux-kernel - Re: [PATCH] lockd: fix races in per-net NSM client handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20121101131457.GC20982@kroah.com>
Date:	Thu, 1 Nov 2012 06:14:57 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Paweł Sikora <pawel.sikora@...k.net>
Cc:	Jonathan Nieder <jrnieder@...il.com>, skinsbursky@...allels.com,
	stable@...r.kernel.org, linux-kernel@...r.kernel.org,
	baggins@...-linux.org, arekm@...-linux.org
Subject: Re: [PATCH] lockd: fix races in per-net NSM client handling

On Thu, Nov 01, 2012 at 07:54:21AM +0100, Paweł Sikora wrote:
> On Wednesday 31 of October 2012 11:22:06 Greg KH wrote:
> > On Wed, Oct 31, 2012 at 11:05:51AM -0700, Jonathan Nieder wrote:
> > > Hi,
> > > 
> > > Greg KH wrote:
> > > > On Wed, Oct 31, 2012 at 06:27:36PM +0100, Paweł Sikora wrote:
> > > 
> > > >> 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?
> > > 
> > > One of
> > > 
> > >   a4ee8d978e47 LOCKD: fix races in nsm_client_get
> > >   e498daa81295 LOCKD: Clear ln->nsm_clnt only when ln->nsm_users is zero
> > > 
> > > both of which were included in v3.6.5.
> > 
> > Ok, Paweł, does 3.6.5 work properly for you?
> 
> ~12h uptime with full cpu/nfs load and all servers with 3.6.5 seem to work stable.

Wonderful, thanks for testing.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/