Re: path_post_lookup

From: Charles Levert (chuckat_private)
Date: Wed Sep 03 2003 - 14:12:29 PDT

  • Next message: Chris Wright: "Re: path_post_lookup"

    On Wed, Sep 03, 2003 at 12:10:44PM -0700, Chris Wright wrote:
    > A similar hook was removed earlier this year in favor of the
    > d_instatiate hook.  Couple questions: 1) have you looked at the thread
    > and verified that you dont' have the same problems?
    Can you send a link to this thread?
    > 2) can't the data
    > that you are getting during post_lookup be associated with the inode and
    > stored as xatrr on-disk?
    This would mean something like storing the identity of all parents (and
    grandparents) of an inode for every one of its paths.  I don't think
    it's workable.  Remember that all I need is the ability to cross mountpoints.
    That would mean storing information on one filesystem about another filesystem,
    assuming there always mounted the same way.  No.
    > On a similar note, since Trond's intents patch the permission hook now
    > has nameidata available.  I'd like to update the API to use nameidata
    > where apropos.  Would this help?
    Is that file_permission or inode_permission?  What would be its prototype?
    linux-security-module mailing list

    This archive was generated by hypermail 2b30 : Wed Sep 03 2003 - 14:14:18 PDT