On Wed, Mar 05, 2008 at 01:54:48PM -0500, David P. Quigley wrote: > This patch introduces two new hooks. One to get all relevant information from > an LSM about an inode an the second given that context to set it on the > inode. The setcontext call takes a flag to indicate if it should set the incore > representation, the ondisk representation or both. This hook is for use in the > labeled NFS code and addresses concerns of how to set security on an inode in a > multi-xattr LSM. I don't quite understand the rationale of the incore vs ondisk flag. Why are these separate? > + int (*inode_setsecctx)(struct dentry *dentry, void *ctx, u32 ctxlen, int flags); > + int (*inode_getsecctx)(struct dentry *dentry, void **ctx, u32 *ctxlen); The dentry in here seems odd given the inode name. Given that we're talking about per-inode security labels here an struct inode * would make more sense to me. -- 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
