On Tue, Feb 18, 2014 at 02:55:59PM +0100, DENIEL Philippe wrote: > I run v9fs as a client on a F20, in front of my Ganesha server (see > http://github.com/nfs-ganesha for details), using 9p.2000L > My acl non-regression test showed errors when I installed a recent > 3.14-rc1 kernel (I got it from kernel.org) on my F20 box. > Investigation showed that the setfacl command line got messy because > setxattr() (called from acl_set_modify() in libattr.so) return a > non-zero value when successful. Further investigation showed that > this behavior seems to come from v9fs_fid_xattr_set() inside > fs/9p/xattr.c in the kernel's source. > > It seems like setxattr syscall does now return the size of the set > xattr, and that seems to be the root cause of my problem. I do not > believe that this change in setxattr is no bug, but a new feature. > So I guess I should patch my libattr and/or glibc to use xattr/acl > with kernel 3.14-rc1. > Question is : where could I get the right version of libattr source > treee (eventually with libacl if needed). New kernel features shouldn't break old libraries--sounds like a bug. --b. -- 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
