From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Trond Myklebust
<trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.org>
Cc: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC][PATCH] Improve NFS use of network and mount namespaces
Date: Tue, 12 May 2009 17:04:39 -0700 [thread overview]
Message-ID: <m13ab97trc.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <1242172010.5407.79.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org> (Trond Myklebust's message of "Tue\, 12 May 2009 19\:46\:50 -0400")
Trond Myklebust <trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.org> 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.
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Trond Myklebust <trond.myklebust@fys.uio.no>
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 17:04:39 -0700 [thread overview]
Message-ID: <m13ab97trc.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <1242172010.5407.79.camel@heimdal.trondhjem.org> (Trond Myklebust's message of "Tue\, 12 May 2009 19\:46\:50 -0400")
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.
Eric
next prev parent reply other threads:[~2009-05-13 0:04 UTC|newest]
Thread overview: 18+ 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 21:51 ` Matt Helsley
[not found] ` <20090512215138.GD3912-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-05-12 22:18 ` Chuck Lever
2009-05-12 22:18 ` Chuck Lever
2009-05-12 23:46 ` Trond Myklebust
2009-05-12 23:46 ` Trond Myklebust
[not found] ` <1242172010.5407.79.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-13 0:04 ` Eric W. Biederman [this message]
2009-05-13 0:04 ` Eric W. Biederman
[not found] ` <m13ab97trc.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2009-05-13 0:13 ` Trond Myklebust
2009-05-13 0:13 ` Trond Myklebust
[not found] ` <1242173604.5407.82.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-13 0:44 ` Matt Helsley
2009-05-13 0:44 ` Matt Helsley
2009-05-13 1:11 ` Eric W. Biederman
2009-05-13 1:11 ` Eric W. Biederman
2009-05-13 0:01 ` Eric W. Biederman
2009-05-13 0:01 ` Eric W. Biederman
[not found] ` <m1fxf97tvt.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2009-05-13 1:05 ` Matt Helsley
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=m13ab97trc.fsf@fess.ebiederm.org \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.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.