From: serue@us.ibm.com
To: serue@us.ibm.com
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-security-module@wirex.com,
Andrew Morton <akpm@osdl.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
James Morris <jmorris@redhat.com>, Chris Wright <chrisw@osdl.org>
Subject: Re: [PATCH -mm 2/3] [LSM] Stacking support for inode_init_security
Date: Mon, 22 Aug 2005 03:19:14 -0500 [thread overview]
Message-ID: <20050822081914.GA25390@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20050822080401.GA26125@sergelap.austin.ibm.com>
This patch, against the 2.6.13-rc6-mm1 stacker, defines the
inode_init_security() hook.
thanks,
-serge
Signed-off-by: Serge Hallyn <serue@us.ibm.com>
--
stacker.c | 35 +++++++++++++++++++++++++++++++++++
1 files changed, 35 insertions(+)
Index: linux-2.6.13-rc6-mm1/security/stacker.c
===================================================================
--- linux-2.6.13-rc6-mm1.orig/security/stacker.c 2005-08-19 17:00:39.000000000 -0500
+++ linux-2.6.13-rc6-mm1/security/stacker.c 2005-08-19 17:01:54.000000000 -0500
@@ -443,6 +443,40 @@ static void stacker_inode_free_security
security_disown_value(h);
}
+static int stacker_inode_init_security(struct inode *inode, struct inode *dir,
+ struct list_head *head)
+{
+ int ret, succ_ret = -EOPNOTSUPP;
+ struct xattr_data *p, *n;
+ struct module_entry *m;
+
+ rcu_read_lock();
+ stack_for_each_entry(m, &stacked_modules, lsm_list) {
+ if (!m->module_operations.inode_init_security)
+ continue;
+ rcu_read_unlock();
+ ret = m->module_operations.inode_init_security(inode,dir,head);
+ rcu_read_lock();
+ if (ret && ret != -EOPNOTSUPP)
+ goto out_free_data;
+ if (ret == 0)
+ succ_ret = 0;
+ }
+ rcu_read_unlock();
+ return succ_ret;
+
+out_free_data:
+ if (!head)
+ return ret;
+ list_for_each_entry_safe(p, n, head, list) {
+ list_del(&p->list);
+ kfree(p->value);
+ kfree(p->name);
+ kfree(p);
+ }
+ return ret;
+}
+
static int stacker_inode_create (struct inode *inode, struct dentry *dentry,
int mask)
{
@@ -1315,6 +1349,7 @@ static struct security_operations stacke
.inode_alloc_security = stacker_inode_alloc_security,
.inode_free_security = stacker_inode_free_security,
+ .inode_init_security = stacker_inode_init_security,
.inode_create = stacker_inode_create,
.inode_link = stacker_inode_link,
.inode_unlink = stacker_inode_unlink,
next prev parent reply other threads:[~2005-08-22 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 8:04 [PATCH -mm] " serue
2005-08-22 8:19 ` serue [this message]
2005-08-22 8:20 ` [PATCH -mm 3/3] " serue
2005-08-22 16:52 ` serue
2005-08-22 23:11 ` Adrian Bunk
2005-08-22 23:14 ` Chris Wright
2005-08-22 19:57 ` serue
2005-08-22 16:50 ` [PATCH -mm] " serue
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=20050822081914.GA25390@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=jmorris@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=sds@tycho.nsa.gov \
/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
all inboxes | Powered by JetHome®