From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Matt Helsley <matthltc@us.ibm.com>,
Containers <containers@lists.osdl.org>,
linux-nfs@vger.kernel.org
Subject: Re: [RFC][PATCH] Improve NFS use of network and mount namespaces
Date: Tue, 12 May 2009 20:13:24 -0400 [thread overview]
Message-ID: <1242173604.5407.82.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <m13ab97trc.fsf@fess.ebiederm.org>
On Tue, 2009-05-12 at 17:04 -0700, Eric W. Biederman wrote:
> Trond Myklebust <trond.myklebust@fys.uio.no> writes:
>
> > Finally, what happens if someone decides to set up a private socket
> > namespace, using CLONE_NEWNET, without also using CLONE_NEWNS to create
> > a private mount namespace? Would anyone have even the remotest chance in
> > hell of figuring out what filesystem is mounted where in the ensuing
> > chaos?
>
> Good question. Multiple NFS servers with the same ip address reachable
> from the same machine sounds about as nasty pickle as it gets.
>
> The only way I can even imagine a setup like that is someone connecting
> to a vpn. So they are behind more than one NAT gateway.
>
> Bleh NAT sucks.
It is doable, though, and it will affect more than just NFS. Pretty much
all networked filesystems are affected.
It begs the question: is there ever any possible justification for
allowing CLONE_NEWNET without implying CLONE_NEWNS?
Trond
next prev parent reply other threads:[~2009-05-13 0:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 21:51 [RFC][PATCH] Improve NFS use of network and mount namespaces Matt Helsley
2009-05-12 22:18 ` Chuck Lever
2009-05-12 23:46 ` Trond Myklebust
2009-05-13 0:04 ` Eric W. Biederman
2009-05-13 0:13 ` Trond Myklebust [this message]
2009-05-13 0:44 ` Matt Helsley
2009-05-13 1:11 ` Eric W. Biederman
2009-05-13 0:01 ` Eric W. Biederman
2009-05-13 1:05 ` 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=1242173604.5407.82.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-nfs@vger.kernel.org \
--cc=matthltc@us.ibm.com \
/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