From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: e2fsprogs: Richacl support
Date: Fri, 16 Oct 2015 19:16:15 -0400 [thread overview]
Message-ID: <20151016231615.GF15011@thunk.org> (raw)
In-Reply-To: <CAHc6FU5s7-t3+jtKDusVFqc542Ag7pEOTUqp1LSxg8_uCPyF=A@mail.gmail.com>
On Fri, Oct 16, 2015 at 06:03:29PM +0200, Andreas Gruenbacher wrote:
>
> could the richacl feature flag please be added to e2fsprogs so that we
> won't end up with incompatible file systems?
>
> https://github.com/andreas-gruenbacher/e2fsprogs
>
> Also, should this really be an incompatible feature flag? With a
> read-only compatibility flag, mounting a richacl filesystem on a
> kernel without richacl support would work but it's not safe --- it
> could grant unwanted access to files. (The same applies to the xfs
> support, etc.)
Richacl's are represented using just extended attributes, right? So
why would this result in incompatible file systems? For similar
reasons we never had a feature flag for Posix ACL's.
Suppose we mounted a file system with richacl's on a kernel that
didn't understand it, and we write to from that non-richacl kernel.
What's the worse that could happen?
- Ted
next prev parent reply other threads:[~2015-10-16 23:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 16:03 e2fsprogs: Richacl support Andreas Gruenbacher
2015-10-16 23:16 ` Theodore Ts'o [this message]
2015-10-17 0:22 ` Andreas Gruenbacher
2015-10-17 14:39 ` Theodore Ts'o
2015-10-17 22:59 ` Dave Chinner
2015-10-18 0:35 ` Theodore Ts'o
2015-10-18 20:46 ` Andreas Gruenbacher
2015-10-18 21:44 ` Theodore Ts'o
2015-10-18 22:46 ` Andreas Gruenbacher
2015-10-19 0:17 ` Theodore Ts'o
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=20151016231615.GF15011@thunk.org \
--to=tytso@mit.edu \
--cc=agruenba@redhat.com \
--cc=linux-ext4@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.