Re: value of task p_pptr in task_alloc_security

From: Seth Arnold (sarnoldat_private)
Date: Sun Nov 10 2002 - 17:04:09 PST

  • Next message: Tim Potter: "Re: value of task p_pptr in task_alloc_security"

    On Sun, Nov 10, 2002 at 08:52:53AM -0800, Tim Potter wrote:
    > My problem is that the p_pptr in the task struct passed points
    > to the grandfather process not the father.  Is this a problem with
    > old versions of LSM?  I'm using the 2.4.18 patch which I realise
    > is quite old.
    
    Tim, in the version of LSM I've got easiest access to, this looks like
    the expected behavior -- the parent task pointer is set well after
    the LSM hook has been called. You can still find the parent task by
    dereferencing current, so it should not be an insurmountable problem.
    
    This is a frequent LSM idiom; many of the hooks that logically require
    the current task need to retrieve it themselves, rather than using it
    as an actual parameter. 
    
    -- 
    "There's an old saying in Tennessee, i know it's in Texas, probably in
    Tennessee, that says, 'Fool me once... shame on ... shame on .. you; but
    fool--you can't get fooled again.'" -- Commander in Chief of the US Military
    
    
    

    _______________________________________________ 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 : Sun Nov 10 2002 - 17:05:39 PST