Hi, I've been hacking a bit on xattr-based ACLs for Ceph. It's all working fine, but I'm having some trouble wiring up the default ACL init code for new inodes (mknod, create, mkdir, and symlink): New ACLs depend on the the ACL of the parent. The ideal location seems to be in fill_inode, but it is unclear how to access the parent inode of the original request from fill_inode because it is receiving the filler information just from a mds reply. Is getting the parent information in fill_inode possible? Alternatively, in each of ceph_mknod, ceph_symlink, etc..., the problem would be solved trivially if the new inode is available because the parent information is provided. For example, in ceph_mknod, on success will dentry->d_inode alway point to the new inode, or is there more async stuff going on? Thanks, Noah -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html