From: Matt Helsley <matthltc@us.ibm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Serge E. Hallyn" <serue@us.ibm.com>,
Linux Containers <containers@lists.linux-foundation.org>,
linux-nfs@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Linux Containers <containers@lists.osdl.org>,
Cedric Le Goater <clg@fr.ibm.com>
Subject: Re: [RFC][PATCH 2/4] sunrpc: Use utsnamespaces
Date: Tue, 06 Jan 2009 15:48:57 -0800 [thread overview]
Message-ID: <1231285737.14345.173.camel@localhost> (raw)
In-Reply-To: <1231284943.8041.8.camel@heimdal.trondhjem.org>
On Tue, 2009-01-06 at 18:35 -0500, Trond Myklebust wrote:
> 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
I originally discarded the idea of relating it to the credentials
because it looked like the credential cache could be flushed at any time
(according to the small portion of the RFC I read) so I was worried we'd
have even worse lifetime issues to deal with.
Cheers,
-Matt
next prev parent reply other threads:[~2009-01-06 23:49 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 1:13 [RFC][PATCH 0/4] utsns: RPC/NFS bug rework Matt Helsley
2009-01-06 1:13 ` [RFC][PATCH 1/4] Remove useless utsname.h includes Matt Helsley
2009-01-06 1:13 ` [RFC][PATCH 2/4] sunrpc: Use utsnamespaces Matt Helsley
2009-01-06 20:02 ` Serge E. Hallyn
2009-01-06 20:20 ` J. Bruce Fields
2009-01-06 21:53 ` Serge E. Hallyn
2009-01-06 23:35 ` Matt Helsley
2009-01-06 22:43 ` Matt Helsley
2009-01-06 20:44 ` Trond Myklebust
2009-01-06 21:58 ` Serge E. Hallyn
2009-01-06 22:42 ` Trond Myklebust
2009-01-07 0:08 ` Matt Helsley
2009-01-07 0:20 ` Trond Myklebust
2009-01-07 0:43 ` Matt Helsley
2009-01-07 1:10 ` Trond Myklebust
2009-01-07 0:20 ` J. Bruce Fields
2009-01-07 0:23 ` Trond Myklebust
2009-01-07 3:44 ` Matt Helsley
2009-01-06 23:04 ` Eric W. Biederman
2009-01-06 23:15 ` Trond Myklebust
2009-01-06 23:32 ` J. Bruce Fields
2009-01-06 23:35 ` Trond Myklebust
2009-01-06 23:48 ` Matt Helsley [this message]
2009-01-06 23:51 ` Chuck Lever
2009-01-06 23:53 ` J. Bruce Fields
2009-01-07 0:07 ` Matt Helsley
2009-01-07 0:55 ` Eric W. Biederman
2009-01-07 0:20 ` Trond Myklebust
2009-01-07 0:20 ` Trond Myklebust
2009-01-07 0:26 ` J. Bruce Fields
2009-01-07 0:38 ` Trond Myklebust
2009-01-07 1:44 ` J. Bruce Fields
2009-01-07 1:50 ` Trond Myklebust
2009-01-07 2:37 ` Eric W. Biederman
2009-01-06 23:30 ` Matt Helsley
2009-01-06 23:18 ` Matt Helsley
2009-01-06 23:43 ` Trond Myklebust
2009-01-06 23:58 ` Matt Helsley
2009-01-06 22:29 ` Chuck Lever
2009-01-07 0:01 ` Serge E. Hallyn
2009-01-06 1:13 ` [RFC][PATCH 3/4] sunrpc: Improve UTS namespace workaround Matt Helsley
2009-01-06 16:02 ` Chuck Lever
2009-01-07 0:28 ` Matt Helsley
2009-01-07 3:02 ` Matt Helsley
2009-01-06 1:13 ` [RFC][PATCH 4/4] Represent RPC Callers Matt Helsley
2009-01-06 13:04 ` Trond Myklebust
2009-01-06 23:05 ` Matt Helsley
-- strict thread matches above, loose matches on Subject: below --
2009-01-07 0:39 [RFC][PATCH 2/4] sunrpc: Use utsnamespaces trond.myklebust
2009-01-07 0:57 ` Matt Helsley
2009-01-07 1:02 ` Trond Myklebust
2009-01-07 1:22 ` Matt Helsley
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=1231285737.14345.173.camel@localhost \
--to=matthltc@us.ibm.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=clg@fr.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=trond.myklebust@fys.uio.no \
/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