From: jim owens <jowens@hp.com>
To: Sriram Ramkrishna <sriram.ramkrishna@gmail.com>,
linux-btrfs@vger.kernel.org
Cc: Chris Mason <chris.mason@oracle.com>, Josef Bacik <josef@redhat.com>
Subject: Re: extended acls..
Date: Tue, 19 May 2009 15:08:22 -0400 [thread overview]
Message-ID: <4A1303A6.1050407@hp.com> (raw)
In-Reply-To: <20090519182110.GA15389@think>
I would suggest another step is more important than starting
with fsdev. You need to talk to the security people.
There is no point in storing and fetching ACLs if there
is no mechanism to operate on them.
filesystems don't create security policies.
jim
next prev parent reply other threads:[~2009-05-19 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 16:50 extended acls Sriram Ramkrishna
2009-05-19 18:06 ` Josef Bacik
2009-05-19 18:16 ` Sriram Ramkrishna
2009-05-19 18:21 ` Chris Mason
2009-05-19 19:08 ` jim owens [this message]
2009-05-19 20:01 ` Claudio Martins
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=4A1303A6.1050407@hp.com \
--to=jowens@hp.com \
--cc=chris.mason@oracle.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sriram.ramkrishna@gmail.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