From: "Paweł Sikora" <pawel.sikora@agmk.net>
To: Greg KH <gregkh@linuxfoundation.org>
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
Date: Wed, 31 Oct 2012 19:02:57 +0100 [thread overview]
Message-ID: <4005626.trvd4a4buj@localhost> (raw)
In-Reply-To: <20121031174946.GA13591@kroah.com>
On Wednesday 31 of October 2012 10:49:46 Greg KH wrote:
> On Wed, Oct 31, 2012 at 06:27:36PM +0100, Paweł Sikora wrote:
> > 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?
BR,
Paweł.
next prev parent reply other threads:[~2012-10-31 18:03 UTC|newest]
Thread overview: 9+ 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 [this message]
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
2012-11-01 13:14 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2012-10-23 19:49 Heads-up: 3.6.2 / 3.6.3 NFS server oops: 3.6.2+ regression? (also an unrelated ext4 data loss bug) Nix
2012-10-24 10:18 ` [PATCH] lockd: fix races in per-net NSM client handling Stanislav Kinsbursky
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=4005626.trvd4a4buj@localhost \
--to=pawel.sikora@agmk.net \
--cc=arekm@pld-linux.org \
--cc=baggins@pld-linux.org \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.