From: David Howells <dhowells@redhat.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: dhowells@redhat.com, Will Drewry <redpig@dataspill.org>,
linux-kernel@vger.kernel.org, James Morris <jmorris@namei.org>,
linux-security-module@vger.kernel.org, morgan@kernel.org
Subject: Re: [RFC][PATCH 1/1] support optional non-VFS capability inheritance without disabling file caps
Date: Tue, 18 Aug 2009 15:07:12 +0100 [thread overview]
Message-ID: <27938.1250604432@redhat.com> (raw)
In-Reply-To: <20090814133225.GB27905@us.ibm.com>
Serge E. Hallyn <serue@us.ibm.com> wrote:
> Heck, maybe we can use the fscache or a stackable fs to provide a view
> of a non-xattr fs with xattrs layered on top. David Howells, does
> that sound doable or would that be an abuse?
You could use fscache, but you would have to deal with the cache not being
available or suddenly going away. Note that fscache does not stack on top of
another fs in Linux in the way it does in Solaris - the non-xattr fs would
have to actively talk to fscache. But it's certainly possible.
David
prev parent reply other threads:[~2009-08-18 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 4:15 [RFC][PATCH 1/1] support optional non-VFS capability inheritance without disabling file caps Will Drewry
2009-08-14 13:32 ` Serge E. Hallyn
2009-08-14 15:40 ` Will Drewry
2009-08-15 17:22 ` Andrew G. Morgan
2009-08-16 4:24 ` Will Drewry
2009-08-17 4:50 ` Andrew G. Morgan
2009-08-17 14:38 ` Will Drewry
2009-08-17 15:26 ` Andrew G. Morgan
2009-08-17 16:48 ` Will Drewry
2009-08-18 0:30 ` Andrew G. Morgan
2009-08-18 14:07 ` David Howells [this message]
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=27938.1250604432@redhat.com \
--to=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=redpig@dataspill.org \
--cc=serue@us.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).