Re: [PATCH v4 0/5] nfsd + hfsplus: introduce generalized version of NFSv4 ACLs <-> POSIX ACLs mapping algorithms

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On May 9, 2013, at 10:10 PM, Myklebust, Trond wrote:

[snip]
> 
> No, there is no requirement that you must support the POSIX acl
> interface in addition to NFSv4/richacls.
> 
> No, supporting a POSIX mapping is not necessarily "better than nothing"
> if it cannot faithfully represent the original NFSv4 acl. Do you at
> least enforce the original acl in permissions checks?

On May 9, 2013, at 10:16 PM, J. Bruce Fields wrote:

[snip]
>> Yes, I understand the nature of such mapping and impossibility of
>> mapping NFSv4 ACLs to POSIX ACLs in some cases. But, as I understand,
>> the richacl patch set is not mainline yet.
> 
> Neither are these patches.  You could pick up the richacl patches and
> work on them instead.  That might be more work, I don't know, but the
> result would certainly be more useful, to many more people....
> 
>> And even if it will be in mainline then a user can have choice to use
>> POSIX ACLs or richacls.
> 
> I actually kinda like the idea of allowing people to use either model
> and translating automatically between them.  But it is complicated, and
> I'm not convinced it's necessary.
> 
>> So, we need to map NFSv4 ACLs <-> POSIX ACLs in hfsplus for the case
>> of using POSIX ACLs model. I think that to have such mapping is better
>> than to have nothing.
> 
> So, in the "better than nothing" spirit, I'll take a look at these, but
> I would still rather we get the richacl stuff done....
> 
> --b.

Yes, I am going to support richacls on hfsplus side when the richacl patch set will be in mainline. How soon it will be in mainline? Why the richacl patch set is not mainline yet? What it should be made for promoting richacl patch set in mainline?

The most of file systems in Linux support POSIX ACL model. So, I think that it makes sense to support POSIX ACLs for HFS+ also. Because it is possible to use POSIX ACLs only under Linux. And such extended attributes may be simply ignored under Mac OS X. So, what good way is for it? I think that we can use "com.apple.system.Security" xattrs for richacl model. And this xattrs will be valid NFSv4 ACLs as for Linux as for Mac OS X. But also it is possible to use "system.posix_acl_access" and "system.posix_acl_default" xattrs as storage of POSIX ACLs that will be treated only under Linux as ACLs. Mac OS X will treat such xattrs as raw xattrs without any real meaning for this OS. What do you think about such suggestion?

With the best regards,
Vyacheslav Dubeyko.

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux