OpenVZ Forum


Home » Mailing lists » Devel » [PATCH] Filesystems visibility control group
Re: [PATCH] Filesystems visibility control group [message #27087 is a reply to message #27076] Fri, 08 February 2008 15:54 Go to previous messageGo to previous message
serue is currently offline  serue
Messages: 750
Registered: February 2006
Senior Member
Quoting Pavel Emelyanov (xemul@openvz.org):
> Dave Hansen wrote:
> > On Thu, 2008-02-07 at 18:04 +0300, Pavel Emelyanov wrote:
> >> Having this proxy is the easiest way to keep the global list and
> >> file_system_type structure (almost) untouched and simplify the code.
> >>
> >> The filesystems.list file syntax is simple: [+-]<name> without
> >> a '\n' at the end. Made for 2.6.24-rc8-mm1
> > 
> > For what would you want this?  What kinds of filesystems would you like
> > to restrict the use of in a container?
> 
> Any you want to.
> 
> E.g. ext3 with its journaling thread. Having 100 containers
> with a journal in each kills the node. 
> E.g. cgroupsfs if you don't want your cgroup create its 
> own ones. 

Ah, so that answers that question - you enforce this by umounting
/cgroups in the container and not letting them remount it?

> E.g. NFS that can stuck on umount and block you container
> on stop.
> 
> > -- Dave
> 
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [PATCH 2.6.24-rc8-mm1 00/15] IPC: code rewrite + new functionalities
Next Topic: [PATCH] [IPV6]: dst_entry leak in ip4ip6_err.
Goto Forum:
  


Current Time: Tue Sep 16 04:49:35 GMT 2025

Total time taken to generate the page: 1.14730 seconds