linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: linuxfs <linux-fsdevel@vger.kernel.org>,
	Alexander Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	Ext2-devel@lists.sourceforge.net,
	Andreas Gruenbacher <agruen@suse.de>,
	Andreas Dilger <adilger@clusterfs.com>,
	Andrew Morton <akpm@osdl.org>, Stephen Tweedie <sct@redhat.com>,
	James Morris <jmorris@redhat.com>, Chris Wright <chrisw@osdl.org>
Subject: Re: [RFC][PATCH 2/3] ext2: Enable atomic inode security labeling
Date: Wed, 13 Jul 2005 15:37:49 -0500	[thread overview]
Message-ID: <1121287069.9235.25.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <1120830914.19035.62.camel@moss-spartans.epoch.ncsc.mil>

On Fri, 2005-07-08 at 09:55 -0400, Stephen Smalley wrote:
> This patch modifies ext2 to call the inode_init_security LSM hook to
> obtain the security attribute for a newly created inode and to set the
> resulting attribute on the new inode.  This parallels the existing
> processing for setting ACLs on newly created inodes.
> 
> Please let me know if you have any comments or suggestions for improvement.
> 
>  fs/ext2/ialloc.c         |    5 +++++
>  fs/ext2/xattr.h          |    1 +
>  fs/ext2/xattr_security.c |   22 ++++++++++++++++++++++
>  3 files changed, 28 insertions(+)
> 
> diff -X /home/sds/dontdiff -rup linux-2.6.13.clean/fs/ext2/ialloc.c linux-2.6.13/fs/ext2/ialloc.c
> --- linux-2.6.13.clean/fs/ext2/ialloc.c	2005-06-17 15:48:29.000000000 -0400
> +++ linux-2.6.13/fs/ext2/ialloc.c	2005-07-06 10:55:37.000000000 -0400
> @@ -614,6 +614,11 @@ got:
>  		DQUOT_FREE_INODE(inode);
>  		goto fail2;
>  	}
> +	err = ext2_init_security(inode,dir);

Won't this be unresolved if CONFIG_EXT2_FS_SECURITY is unset?
xattr_security.c won't be compiled at all.  The ext3 patch has the same
problem.

BTW, I'm working on a patch for jfs.  It's a little more complicated
since jfs's xattr code creates a transaction down in the lower level
code.  I'm going to have to restructure it so the caller creates the
transaction and passes down the tid.

> +	if (err) {
> +		DQUOT_FREE_INODE(inode);
> +		goto fail2;
> +	}
>  	mark_inode_dirty(inode);
>  	ext2_debug("allocating inode %lu\n", inode->i_ino);
>  	ext2_preread_inode(inode);
> diff -X /home/sds/dontdiff -rup linux-2.6.13.clean/fs/ext2/xattr.h linux-2.6.13/fs/ext2/xattr.h
> --- linux-2.6.13.clean/fs/ext2/xattr.h	2005-06-17 15:48:29.000000000 -0400
> +++ linux-2.6.13/fs/ext2/xattr.h	2005-07-06 10:55:37.000000000 -0400
> @@ -64,6 +64,7 @@ extern struct xattr_handler ext2_xattr_s
>  
>  extern ssize_t ext2_listxattr(struct dentry *, char *, size_t);
>  
> +extern int ext2_init_security(struct inode *inode, struct inode *dir);
>  extern int ext2_xattr_get(struct inode *, int, const char *, void *, size_t);
>  extern int ext2_xattr_set(struct inode *, int, const char *, const void *, size_t, int);
>  
> diff -X /home/sds/dontdiff -rup linux-2.6.13.clean/fs/ext2/xattr_security.c linux-2.6.13/fs/ext2/xattr_security.c
> --- linux-2.6.13.clean/fs/ext2/xattr_security.c	2005-06-17 15:48:29.000000000 -0400
> +++ linux-2.6.13/fs/ext2/xattr_security.c	2005-07-06 10:56:20.000000000 -0400
> @@ -8,6 +8,7 @@
>  #include <linux/fs.h>
>  #include <linux/smp_lock.h>
>  #include <linux/ext2_fs.h>
> +#include <linux/security.h>
>  #include "xattr.h"
>  
>  static size_t
> @@ -45,6 +46,27 @@ ext2_xattr_security_set(struct inode *in
>  			      value, size, flags);
>  }
>  
> +int
> +ext2_init_security(struct inode *inode, struct inode *dir)
> +{
> +	int err;
> +	size_t len;
> +	void *value;
> +	char *name;
> +
> +	err = security_inode_init_security(inode, dir, &name, &value, &len);
> +	if (err) {
> +		if (err == -EOPNOTSUPP)
> +			return 0;
> +		return err;
> +	}
> +	err = ext2_xattr_set(inode, EXT2_XATTR_INDEX_SECURITY, 
> +			     name, value, len, 0);
> +	kfree(name);
> +	kfree(value);
> +	return err;
> +}
> +
>  struct xattr_handler ext2_xattr_security_handler = {
>  	.prefix	= XATTR_SECURITY_PREFIX,
>  	.list	= ext2_xattr_security_list,
> 
-- 
David Kleikamp
IBM Linux Technology Center



-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar

  parent reply	other threads:[~2005-07-13 20:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08 13:25 [RFC][PATCH 0/3] Enable atomic inode security labeling Stephen Smalley
2005-07-08 13:48 ` [RFC][PATCH 1/3] security: " Stephen Smalley
2005-07-08 13:55 ` [RFC][PATCH 2/3] ext2: " Stephen Smalley
2005-07-10 23:39   ` Christoph Hellwig
2005-07-11 12:53     ` Stephen Smalley
2005-07-12  2:29       ` Christoph Hellwig
2005-07-13 20:37   ` Dave Kleikamp [this message]
2005-07-13 20:41     ` Stephen Smalley
2005-07-13 20:50     ` Andrew Morton
2005-07-08 13:58 ` [RFC][PATCH 3/3] ext3: " Stephen Smalley
2005-07-11 16:07   ` Stephen C. Tweedie
2005-07-11 16:14     ` Jan Kara
2005-07-11 16:50       ` Stephen C. Tweedie
2005-07-12 14:15         ` [Ext2-devel] " Jan Kara
2005-07-10 23:40 ` [RFC][PATCH 0/3] " Christoph Hellwig
2005-07-11 13:31   ` Stephen Smalley
2005-07-12  2:32     ` Christoph Hellwig
2005-07-13 15:05 ` [RFC][PATCH 2.6.13-rc2-mm2] tmpfs: " Stephen Smalley
2005-07-14 19:29   ` [RFC][PATCH] Remove security_inode_post_create/mkdir/symlink/mknod hooks Stephen Smalley
2005-07-14 19:41     ` Chris Wright
2005-07-14 20:51       ` Stephen Smalley
2005-07-14 16:16 ` [RFC][PATCH 0/2] JFS atomic inode security labeling Dave Kleikamp
2005-07-14 16:19   ` [RFC][PATCH 1/2] JFS atomic xattr/acl handling Dave Kleikamp
2005-07-14 16:20   ` [RFC][PATCH 2/2] JFS atomic inode security labeling Dave Kleikamp
2005-07-14 16:26   ` [RFC][PATCH 0/2] " Dave Kleikamp

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=1121287069.9235.25.camel@kleikamp.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --cc=Ext2-devel@lists.sourceforge.net \
    --cc=adilger@clusterfs.com \
    --cc=agruen@suse.de \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=jmorris@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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).