public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Josef Bacik <josef@redhat.com>
Cc: Sriram Ramkrishna <sriram.ramkrishna@gmail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: extended acls..
Date: Tue, 19 May 2009 14:21:10 -0400	[thread overview]
Message-ID: <20090519182110.GA15389@think> (raw)
In-Reply-To: <20090519180608.GC7472@dhcp231-156.rdu.redhat.com>

On Tue, May 19, 2009 at 02:06:08PM -0400, Josef Bacik wrote:
> On Tue, May 19, 2009 at 09:50:42AM -0700, Sriram Ramkrishna wrote:
> > Howdy,
> > 
> > I'm curious if there is any plans to add extended acls ala AFS?  The
> > reason I ask is that it seems in Linux we don't seem have moved off of
> > POSIX style acls and I think there is definitely at least from my
> > perspective that having a richer set of acl would be needed.  For
> > instance, we would need acls to deal with controlled countries if we
> > are sharing data with them etc.  It is a big shame that there is no
> > RFC for extended ACLs.
> > 
> > Also, I would like to help out with development, I'm a newbie as far
> > as kernel level hacking goes.  If there is a place I can go that I can
> > start off small that would be lovely.
> >
> 
> Extending ACLs beyond POSIX ACLs is a more generic topic that should probably be
> discussed elsewhere, perhaps linux-fsdevel.  Its not going to do much good to
> implement yet another extended ACL implementation in BTRFS if no other Linux fs
> has the ability to use the same feature, so figuring out the details of
> extending ACLs should be done before doing them in btrfs.  Thanks,
> 

I'd agree with this.  The idea behind the btrfs acl/xattr implementation
is to be generic enough to support whatever new ideas people come up
with.  But, I don't intend on driving new acl frameworks through btrfs
before they are available in other filesystems.

-chris


  parent reply	other threads:[~2009-05-19 18:21 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 [this message]
2009-05-19 19:08     ` jim owens
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=20090519182110.GA15389@think \
    --to=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