From: Chris Mason <chris.mason@oracle.com>
To: David Bruzos <David.Bruzos@jaxport.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Optionally enforced time-based ACLs for BTRFS
Date: Thu, 26 Apr 2012 16:04:23 -0400 [thread overview]
Message-ID: <20120426200423.GR22794@shiny> (raw)
In-Reply-To: <DE6EA944EF16AF4CA4C0D1856C83808006C7F05E96@ex7>
On Thu, Apr 26, 2012 at 03:30:39PM -0400, David Bruzos wrote:
> Hi BTRFS folks: In my organization, many use cases exist for a
> time-based honoring field for FS ACLs. I've done some brief research
> regarding this topic, but I was unable to find any reference to such a
> thing in any file system. I understand that a feature like time-based
> honoring for ACLs may arguably be something that should exist in
> higher layers (E.G. some document management system), but on the other
> hand, I see no real reason that an extra ACL field that would allow
> for time-based granting/removing of permissions to some user would be
> a problem.
One of the interesting thing about linux acls is the filesystems don't
really implement acls. We implement xattrs, and the higher layers stuff
acls into them. In a few key spots we tell the higher layers how to do
that, and we also call back into the higher layers for permission
checks.
This is a long way of saying the changes would have to happen in the
generic acl code. This is a good thing, it will get much more review
that way.
I'd suggest posting this to linux-fsdevel.
-chris
next prev parent reply other threads:[~2012-04-26 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 19:30 Optionally enforced time-based ACLs for BTRFS David Bruzos
2012-04-26 20:04 ` Chris Mason [this message]
2012-04-26 21:27 ` David Bruzos
2012-04-27 14:57 ` Chris Mason
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=20120426200423.GR22794@shiny \
--to=chris.mason@oracle.com \
--cc=David.Bruzos@jaxport.com \
--cc=linux-btrfs@vger.kernel.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.