On Sun, Sep 20, 2009 at 03:13:28PM +1000, James Morris wrote: > As a first step, it keeps the semantics simple, and provides a direct > mapping between the userland API and the NFS protocol. System level > xattrs may have semantics which extend beyond the simple NFS xattr > protocol (e.g. full security labeling as we've previously discussed & > documented needs to convey more than just object labels). > > Some xattr uses are internal local interfaces, such as with Linux ACLs, > where xattrs are used internally for storing the ACL data, but the exposed > API is quite different (as is the NFS protocol). > > We can go beyond user.*, but I think each system-level xattr exposed via > NFS will need to be considered on a case-by-case basis. Note that the mapping should be really simple. Both the NFS protocol and XFS implement the same IRIX-xattr format that has a numerical namespace instead of the string prefix Linux has. If you just use the same mapping as XFS it should not have interoperability problems. -- 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
