[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FA345DA4F4AE44899BD2B03EEEC2FA908FA7F55@SACEXCMBX04-PRD.hq.netapp.com>
Date: Fri, 14 Sep 2012 17:38:18 +0000
From: "Myklebust, Trond" <Trond.Myklebust@...app.com>
To: Chuck Lever <chuck.lever@...cle.com>
CC: Stanislav Kinsbursky <skinsbursky@...allels.com>,
"bfields@...ldses.org" <bfields@...ldses.org>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"devel@...nvz.org" <devel@...nvz.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jlayton@...hat.com" <jlayton@...hat.com>
Subject: Re: [PATCH 0/3] lockd: use per-net refrence-counted NSM clients
On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote:
> What happens if statd is restarted?
Nothing unusual. Why?
> Sent from my iPhone
>
> On Sep 14, 2012, at 10:25 AM, Stanislav Kinsbursky <skinsbursky@...allels.com> wrote:
>
> > This is a bug fix for https://bugzilla.redhat.com/show_bug.cgi?id=830862.
> >
> > The problem is that with NFSv4 mount in container (with separated mount
> > namesapce) and active lock on it, dying child reaped of this container will
> > try to umount NFS and doing this will try to create RPC client to send
> > unmonitor request to statd.
> > But creation of RCP client requires valid current->nsproxy (for operation with
> > utsname()) and during umount on child reaper exit it's equal to zero.
> >
> > Proposed solution is to introduce refrence-counter per-net NSM client, which
> > is created on fist monitor call and destroyed after the lst monitor call.
> >
> > The following series implements...
> >
> > ---
> >
> > Stanislav Kinsbursky (3):
> > lockd: use rpc client's cl_nodename for id encoding
> > lockd: per-net NSM client creation and destruction helpers introduced
> > lockd: create and use per-net NSM RPC clients on MON/UNMON requests
> >
> >
> > fs/lockd/mon.c | 91 +++++++++++++++++++++++++++++++++++++++++++-----------
> > fs/lockd/netns.h | 4 ++
> > fs/lockd/svc.c | 1 +
> > 3 files changed, 77 insertions(+), 19 deletions(-)
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> > the body of a message to majordomo@...r.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@...app.com
www.netapp.com
Powered by blists - more mailing lists