From: John Ogness <dazukocode@ogness.net>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
malware-list@lists.printk.net, eparis@redhat.com,
hch@infradead.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCHv2 3/5] VFS: DazukoFS, stackable-fs, file access control
Date: Tue, 17 Feb 2009 09:55:30 +0100 [thread overview]
Message-ID: <86fxidfnnh.fsf@johno.fn.ogness.net> (raw)
In-Reply-To: <m1k57vcsr1.fsf@fess.ebiederm.org> (Eric W. Biederman's message of "Thu\, 12 Feb 2009 12\:20\:02 -0800")
On 2009-02-12, ebiederm@xmission.com (Eric W. Biederman) wrote:
>> Patch 3: Creates /dev/dazukofs.ctrl to allow for groups to be added,
>> listed, and deleted. Also, /dev/dazukofs.[0-9] devices are
>> created to support multiple groups.
>
> Great another global namespace for process groups. What is your
> plan for making this work in a container?
It is good that you mention it. This is something that I totally
missed. I am not yet certain what kind of a role DazukoFS should have
within containers. I need to learn the container API's and see what
kinds of options are available. The next patchset (which it seems
won't be coming too quickly now) will address this in some form.
John Ogness
next prev parent reply other threads:[~2009-02-17 8:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 19:14 [PATCHv2 0/5] VFS: DazukoFS, stackable-fs, file access control John Ogness
2009-02-03 19:15 ` [PATCHv2 1/5] " John Ogness
2009-02-03 19:17 ` [PATCHv2 2/5] " John Ogness
2009-02-03 19:18 ` [PATCHv2 3/5] " John Ogness
2009-02-03 19:19 ` [PATCHv2 4/5] " John Ogness
2009-02-03 19:20 ` [PATCHv2 5/5] " John Ogness
2009-02-12 20:24 ` Eric W. Biederman
2009-02-12 20:20 ` [PATCHv2 3/5] " Eric W. Biederman
2009-02-17 8:55 ` John Ogness [this message]
2009-02-18 0:41 ` Eric W. Biederman
2009-02-21 18:11 ` [malware-list] " Frantisek Hrbata
2009-02-12 16:00 ` [PATCHv2 2/5] " Jan Engelhardt
2009-02-13 19:33 ` John Ogness
2009-02-12 20:14 ` Eric W. Biederman
2009-02-13 19:39 ` John Ogness
2009-02-12 15:27 ` [PATCHv2 1/5] " Jan Engelhardt
2009-02-12 15:31 ` Al Viro
2009-02-12 15:59 ` Jan Engelhardt
2009-02-12 16:47 ` Al Viro
2009-02-13 19:31 ` John Ogness
2009-02-13 19:48 ` Al Viro
2009-02-13 20:00 ` Jan Engelhardt
2009-02-13 20:25 ` Al Viro
2009-02-14 8:43 ` John Ogness
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=86fxidfnnh.fsf@johno.fn.ogness.net \
--to=dazukocode@ogness.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--cc=eparis@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malware-list@lists.printk.net \
--cc=viro@zeniv.linux.org.uk \
/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