From: "Paweł Sikora" <pawel.sikora@agmk.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
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
Date: Thu, 01 Nov 2012 07:54:21 +0100 [thread overview]
Message-ID: <46616972.aF1r9eoRhb@localhost> (raw)
In-Reply-To: <20121031182206.GB1542@kroah.com>
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.
next prev parent reply other threads:[~2012-11-01 6:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 17:27 [PATCH] lockd: fix races in per-net NSM client handling Paweł Sikora
2012-10-31 17:49 ` Greg KH
2012-10-31 18:02 ` Paweł Sikora
2012-10-31 18:18 ` Myklebust, Trond
2012-10-31 18:05 ` Jonathan Nieder
2012-10-31 18:22 ` Greg KH
2012-11-01 6:54 ` Paweł Sikora [this message]
2012-11-01 13:14 ` Greg KH
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=46616972.aF1r9eoRhb@localhost \
--to=pawel.sikora@agmk.net \
--cc=arekm@pld-linux.org \
--cc=baggins@pld-linux.org \
--cc=gregkh@linuxfoundation.org \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skinsbursky@parallels.com \
--cc=stable@vger.kernel.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).