Re: 2.6.10-rc2-mm4

[Stephen Smalley]

On Tue, 2004-12-07 at 14:57, Jeff Mahoney wrote:
> However, selinux itself accesses inode lists internally that circumvent
> this. I believe I caught the major case that causes this, but I'd prefer
> someone with more intimate knowledge of selinux verify.

inodes are only added to the list (prior to superblock security
initialization, e.g. before initial policy load or during get_sb) by
inode_doinit_with_dentry, which in turn is called from
selinux_d_instantiate.  So if you've marked the inode private prior to
the d_instantiate call on it, and changed security_d_instantiate to not
call the security module for private inodes, how would a private inode
ever get into that list?

-- 
Stephen Smalley <sds@xxxxxxxxxxxxxx>
National Security Agency

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/