Re: Locking task->security

From: Stephen Smalley (sdsat_private)
Date: Fri Aug 31 2001 - 05:43:32 PDT

  • Next message: Stephen Smalley: "Re: New patch for bdflush and syslog"

    On Fri, 31 Aug 2001, Stephen Smalley wrote:
    
    > This is unlikely to be a problem with current->security.  A better 
    > example is inode->i_security or sb->s_security, where you are more 
    > likely to have a race on the allocation of the security object.
    
    I should probably mention that this race condition isn't SMP-related.
    It can occur in the UP case if you use a blocking memory allocation
    for the security blob and perform the allocation in a precondition
    function when you catch an object without a security blob.  With
    regard to locking for SMP, we haven't really addressed that issue
    in the SELinux hook functions yet.
    
    --
    Stephen D. Smalley, NAI Labs
    ssmalleyat_private
    
    
    
    
    
    _______________________________________________
    linux-security-module mailing list
    linux-security-moduleat_private
    http://mail.wirex.com/mailman/listinfo/linux-security-module
    



    This archive was generated by hypermail 2b30 : Fri Aug 31 2001 - 05:44:36 PDT