From: Eric Biggers <ebiggers3@gmail.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: "Christoph Hellwig" <hch@lst.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>,
linux-fsdevel@vger.kernel.org, "Jan Kara" <jack@suse.cz>
Subject: Re: [PATCH] hfsplus: drop ACL support
Date: Tue, 17 Jul 2018 11:34:34 -0700 [thread overview]
Message-ID: <20180717183434.GD75957@gmail.com> (raw)
In-Reply-To: <1531852157.18827.9.camel@dubeyko.com>
On Tue, Jul 17, 2018 at 11:29:17AM -0700, Viacheslav Dubeyko wrote:
> On Tue, 2018-07-17 at 15:18 +0200, Christoph Hellwig wrote:
> > On Mon, Jul 16, 2018 at 05:07:48PM -0700, Andrew Morton wrote:
> > >
> > > On Sat, 14 Jul 2018 12:11:03 -0700 Viacheslav Dubeyko <slava@dubeyk
> > > o.com> wrote:
> > >
> > > >
> > > > On Sat, 2018-07-14 at 16:06 -0300, Ernesto A. Fern�ndez wrote:
> > > > >
> > > > > The HFS+ Access Control Lists have not worked at all for the
> > > > > past
> > > > > five
> > > > > years, and nobody seems to have noticed. Besides, POSIX draft
> > > > > ACLs
> > > > > are
> > > > > not compatible with MacOS. Drop the feature entirely.
> > > > >
> > > > Bugs need to be fixed but not to drop. Otherwise, it needs to
> > > > drop the
> > > > whole HFS+ support from the kernel.
> > > Yes, we could make it depend on BROKEN and hope that someone comes
> > > along and fixes it - there's little cost in carrying such a thing.
> > >
> > > Or maybe it can never work for some reason and should indeed be
> > > dropped, I don't know.��I was interested in understanding the
> > > reasoning
> > > behind hch's ack, but I can't find it on linux-fs-devel.��Help?
> > The issue is that hfsplus supports it's own NFSv4-like ACLs, which
> > are nothing like the Posix ACLs supported by the Linux driver.��Or
> > in other words: they were always a Linux-only incompatible extension
> > that should never have been merged.
>
>
> The richacls subsystem was not in the kernel at the time of ACL support
> implementation. So, the idea of Linux-like ACLs in HFS+ was not to be
> compatible with MAC OS X. The goal was to provide the opportunity to
> use the ACLs only in Linux if anybody likes this. The MAC OS X will
> ignore such xattrs.
>
> As far as I can see, the ACL subsystem in HFS+ stops to work after
> Christoph's reworking the ACL subsystem in the Linux. So, we have
> richacls subsystem in the Linux kernel now. I believe that it makes
> sense to implement the richacls support in HFS+ at first. Then we can
> discuss to drop or not to drop the current ACL implementation in HFS+.�
Richacls are *not* in the kernel yet.
- Eric
next prev parent reply other threads:[~2018-07-17 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 19:06 [PATCH] hfsplus: drop ACL support Ernesto A. Fernández
2018-07-14 19:11 ` Viacheslav Dubeyko
2018-07-17 0:07 ` Andrew Morton
2018-07-17 0:21 ` Ernesto A. Fernández
2018-07-27 17:48 ` Ernesto A. Fernández
2018-07-17 13:18 ` Christoph Hellwig
2018-07-17 18:29 ` Viacheslav Dubeyko
2018-07-17 18:34 ` Eric Biggers [this message]
2018-07-14 19:29 ` Viacheslav Dubeyko
-- strict thread matches above, loose matches on Subject: below --
2017-12-03 1:41 Ernesto A. Fernández
2017-12-03 20:59 ` Viacheslav Dubeyko
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=20180717183434.GD75957@gmail.com \
--to=ebiggers3@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ernesto.mnd.fernandez@gmail.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.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 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.