On Tue, Sep 25, 2012 at 02:57:04PM +0400, Vyacheslav Dubeyko wrote: > As I can understand, you are talking about using xattr_handler's for > dispatching of processing of extended attributes with such complex names > as "system.posix_acl_access" and so on. Am I correct? > > The HFS+ has such peculiarities that you can name extended attribute as > you want. And name of extended attribute can keep in Attributes Tree > without any prefixes (for example, as "test"). Moreover, it is not used > such prefixes as "user." or "system." under Mac OS X. But we will have to use them under Linux. The whole xattr mechanism is built around the model that we decide policies, including most importantly access control, based on these prefixes. In retrospective I think the string prefixes are a horrible idea and a simple binary flag namespace as done by e.g. IRIX or FreeBSD would have made everyones life a heck lot simpler, but that's not what we implemented 10 years ago. > However, it exists under Mac OS X special prefix "com.apple." (for > example, "com.apple.FinderInfo"). So, you suggest to add definition of > additional prefixes "com." and "apple." in include/linux/xattr.h and to > add xattr_handler's for these two prefixes. Am I correct? No. I'd suggest mapping any free-form attributes in hfsplus into user.* in the syscall namespace, while only mapping a few that needs special treatment into system.* or similar. Using the proper helpers will make this actually readable at least. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
