Re: [patch 3/4] Network namespaces: IPv4 FIB/routing in namespaces

Kirill Korotaev wrote:

quoted

quoted

quoted

quoted

Structures related to IPv4 rounting (FIB and routing cache)
are made per-namespace.

Hi Andrey,

if the ressources are private to the namespace, how do you will 
handle NFS mounted before creating the network namespace ? Do you 
take care of that or simply assume you can't access NFS anymore ?

This is a question that brings up another level of interaction between
networking and the rest of kernel code.
Solution that I use now makes the NFS communication part always run in
the root namespace.  This is discussable, of course, but it's a far more
complicated matter than just device lists or routing :)

if we had containers (not namespaces) then it would be also possible to 
run NFS in context of the appropriate container and thus each user could 
 mount NFS itself with correct networking context.

I was asking the question because in some case, we want a lightweight 
container for running applications (aka application container) who need 
to share the filesystem and it will be too bad to have a network 
namespace which brings isolation and prevents to implement application 
containers. By the way, I agree from a point of view of a system 
container, a complete network isolation is perfect.

Regards.

Daniel.