Zakaria ElQotbi: > I think this field must be the same as the underlying filesystem, instead of > creating new fresh one at ovl_new_inode() which give an UNLABELED sid. When two inodes refers to a single inode_security_struct (i_security), won't it cause a "double free" problem? J. R. Okajima -- 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