kernel.git/fs/ceph/xattr.c, branch linux-3.17.y

ceph: fix sizeof(struct tYpO *) typo

2014-07-28T09:29:27Z

struct ceph_xattr -> struct ceph_inode_xattr Reported-by: Toralf Förster Signed-off-by: Ilya Dryomov Reviewed-by: Alex Elder

ceph: remove redundant memset(0)

2014-07-28T09:28:33Z

xattrs array of pointers is allocated with kcalloc() - no need to memset() it to 0 right after that. Signed-off-by: Ilya Dryomov Reviewed-by: Alex Elder

ceph: don't include ceph.{file,dir}.layout vxattr in listxattr()

2014-04-05T04:07:21Z

This avoids 'cp -a' modifying layout of new files/directories. Signed-off-by: Yan, Zheng

ceph: check buffer size in ceph_vxattrcb_layout()

2014-04-05T04:07:19Z

If buffer size is zero, return the size of layout vxattr. If buffer size is not zero, check if it is large enough for layout vxattr. Signed-off-by: Yan, Zheng

ceph: do not chain inode updates to parent fsync

2014-04-03T02:33:52Z

The fsync(dirfd) only covers namespace operations, not inode updates. We do not need to cover setattr variants or O_TRUNC. Reported-by: Al Viro Signed-off-by: Sage Weil Reviewed-by: Yan, Zheng

ceph: fix ceph_removexattr()

2014-02-17T20:37:10Z

Signed-off-by: Yan, Zheng

ceph: remove xattr when null value is given to setxattr()

2014-02-17T20:37:09Z

For the setxattr request, introduce a new flag CEPH_XATTR_REMOVE to distinguish null value case from the zero-length value case. Signed-off-by: Yan, Zheng

ceph: properly handle XATTR_CREATE and XATTR_REPLACE

2014-02-17T20:37:05Z

return -EEXIST if XATTR_CREATE is set and xattr alread exists. return -ENODATA if XATTR_REPLACE is set but xattr does not exist. Signed-off-by: Yan, Zheng

ceph: Fix up after semantic merge conflict

2014-01-29T02:06:18Z

The previous ceph-client merge resulted in ceph not even building, because there was a merge conflict that wasn't visible as an actual data conflict: commit 7221fe4c2ed7 ("ceph: add acl for cephfs") added support for POSIX ACL's into Ceph, but unluckily we also had the VFS tree change a lot of the POSIX ACL helper functions to be much more helpful to filesystems (see for example commits 2aeccbe957d0 "fs: add generic xattr_acl handlers", 5bf3258fd2ac "fs: make posix_acl_chmod more useful" and 37bc15392a23 "fs: make posix_acl_create more useful") The reason this conflict wasn't obvious was many-fold: because it was a semantic conflict rather than a data conflict, it wasn't visible in the git merge as a conflict. And because the VFS tree hadn't been in linux-next, people hadn't become aware of it that way. And because I was at jury duty this morning, I was using my laptop and as a result not doing constant "allmodconfig" builds. Anyway, this fixes the build and generally removes a fair chunk of the Ceph POSIX ACL support code, since the improved helpers seem to match really well for Ceph too. But I don't actually have any way to *test* the end result, and I was really hoping for some ACK's for this. Oh, well. Not compiling certainly doesn't make things easier to test, so I'm committing this without the acks after having waited for four hours... Plus it's what I would have done for the merge had I noticed the semantic conflict.. Reported-by: Dave Jones Cc: Sage Weil Cc: Guangliang Zhao Cc: Li Wang Cc: Christoph Hellwig Cc: Al Viro Signed-off-by: Linus Torvalds

ceph: add acl for cephfs

2013-12-31T18:32:01Z

Signed-off-by: Guangliang Zhao Reviewed-by: Li Wang Reviewed-by: Zheng Yan