Re: 2.6.10-rc2-mm4

[Stephen Smalley]

On Wed, 2004-12-01 at 20:01, Chris Wright wrote:
> This sounds a bit better.  BTW, which is the call chain that locks? smth like
> open->permission->selinux_hook_does_getxattr->reiser_getxattr->open->permission?

IIRC, the original deadlock call chain was when SELinux tried to set the
security attribute on a newly created file from the post_create hooks. 
Looked something like (SELinux) post_create -> reiser_setxattr -> ... ->
open_xa_dir -> reiserfs_mkdir -> d_instantiate ->
selinux_d_instantiate() -> inode_doinit_with_dentry() ->
reiser_getxattr.  First reported in
http://marc.theaimsgroup.com/?l=linux-kernel&m=108625196416654&w=2, but
that only addressed the deadlock issue, not the permission checking
problem.

-- 
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/