linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bill4carson <bill4carson@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: Question about inode and dentry
Date: Fri, 01 Nov 2013 15:24:09 +0800	[thread overview]
Message-ID: <52735719.1070408@gmail.com> (raw)

Hi, all

Really new to fs area ;) I'm trying to port Umbrella project based on linux-2.6.11,
which implementing Process-Based Access Control (PBAC) to linux-2.6.34.

The key of Umbrella project is to restrict process access from some directory/files,
these restriction can be fetched from /proc/umbrella. First the directory/file path is
parsed from struct dentry, then every inode operation finally has to be checked against
the restrictions with current accessed path involved. This basically how it works.

In linux-2.6.11, struct dentry is used by nd->dentry.

int permission(struct inode *inode, int mask, struct nameidata *nd)
   -> security_inode_permission
      -> security_ops->inode_permission




But in linux-2.6.34, struct nameidata is not used any more, how can I get proper struct
dentry from inode?

int inode_permission(struct inode *inode, int mask)
   -> security_inode_permission
       -> security_ops->inode_permission


Thanks in advance.

-- 
八百里秦川尘土飞扬,三千万老陕齐吼秦腔。

--bill
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2013-11-01  7:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01  7:24 bill4carson [this message]
2013-11-01 12:24 ` Question about inode and dentry Tetsuo Handa
2013-11-01 15:07 ` Richard Weinberger
2013-11-08  8:25   ` bill4carson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52735719.1070408@gmail.com \
    --to=bill4carson@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).