[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1231284943.8041.8.camel@heimdal.trondhjem.org>
Date: Tue, 06 Jan 2009 18:35:43 -0500
From: Trond Myklebust <trond.myklebust@....uio.no>
To: "J. Bruce Fields" <bfields@...ldses.org>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
"Serge E. Hallyn" <serue@...ibm.com>,
Matt Helsley <matthltc@...ibm.com>,
Linux Containers <containers@...ts.linux-foundation.org>,
linux-nfs@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Chuck Lever <chuck.lever@...cle.com>,
Linux Containers <containers@...ts.osdl.org>,
Cedric Le Goater <clg@...ibm.com>
Subject: Re: [RFC][PATCH 2/4] sunrpc: Use utsnamespaces
On Tue, 2009-01-06 at 18:32 -0500, J. Bruce Fields wrote:
> On Tue, Jan 06, 2009 at 06:15:34PM -0500, Trond Myklebust wrote:
> > On Tue, 2009-01-06 at 15:04 -0800, Eric W. Biederman wrote:
> > > That implies to me you want to capture the value at mount time, and to
> > > pass it in to the rpc_call creation, and only at very specific well
> > > defined points where we interact with user space should we examine
> > > current->utsname(). At which point there should be no question
> > > of current->utsname() is valid as the user space process is alive.
> >
> > Why pretend that the filesystem is owned by a particular namespace? It
> > can, and will be shared among many containers...
>
> If the only purpose of this is to fill in the auth_unix cred then
> shouldn't it be part of whatever cred structures are passed around?
So how does tracking it in a shared structure like the rpc_client help?
If you consider it to be part of the cred, then it needs to be tracked
in the cred...
Trond
--
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/
Powered by blists - more mailing lists