All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: Dave Hansen <haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH] Filesystems visibility control group
Date: Fri, 08 Feb 2008 11:13:31 +0300	[thread overview]
Message-ID: <47AC0F2B.3070903@openvz.org> (raw)
In-Reply-To: <1202404169.9065.21.camel-FpcvD5N4B9G9xGwK5P7XA+TW4wlIGRCZ@public.gmane.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. 
E.g. NFS that can stuck on umount and block you container
on stop.

> -- Dave

  parent reply	other threads:[~2008-02-08  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 15:04 [PATCH] Filesystems visibility control group Pavel Emelyanov
     [not found] ` <47AB1E14.1080203-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-02-07 17:09   ` Dave Hansen
     [not found]     ` <1202404169.9065.21.camel-FpcvD5N4B9G9xGwK5P7XA+TW4wlIGRCZ@public.gmane.org>
2008-02-08  8:13       ` Pavel Emelyanov [this message]
     [not found]         ` <47AC0F2B.3070903-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-02-08 15:54           ` Serge E. Hallyn
2008-02-07 18:13   ` Paul Jackson

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=47AC0F2B.3070903@openvz.org \
    --to=xemul-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=haveblue-r/Jw6+rmf7HQT0dZR+AlfA@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.