The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Xiaotian Feng <dfeng@redhat.com>
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, Mimi Zohar <zohar@us.ibm.com>,
	James Morris <jmorris@namei.org>, Eric Paris <eparis@redhat.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	"Amit K. Arora" <amitarora@in.ibm.com>
Subject: Re: [PATCH] security: fix error return path in ima_inode_alloc
Date: Wed, 24 Feb 2010 10:41:30 -0500	[thread overview]
Message-ID: <1267026090.2618.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1267007942-315-1-git-send-email-dfeng@redhat.com>

On Wed, 2010-02-24 at 18:39 +0800, Xiaotian Feng wrote:
> If radix_tree_preload is failed in ima_inode_alloc, we don't need
> radix_tree_preload_end because kernel is alread preempt enabled
> 
> Signed-off-by: Xiaotian Feng <dfeng@redhat.com>

Signed-off-by: Mimi Zohar <zohar@us.ibm.com>

thanks,
Mimi

> Cc: Mimi Zohar <zohar@us.ibm.com>
> Cc: James Morris <jmorris@namei.org>
> Cc: Eric Paris <eparis@redhat.com>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: Amit K. Arora <amitarora@in.ibm.com>
> ---
>  security/integrity/ima/ima_iint.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/security/integrity/ima/ima_iint.c b/security/integrity/ima/ima_iint.c
> index 0d83edc..2d4d05d 100644
> --- a/security/integrity/ima/ima_iint.c
> +++ b/security/integrity/ima/ima_iint.c
> @@ -63,12 +63,11 @@ int ima_inode_alloc(struct inode *inode)
>  	spin_lock(&ima_iint_lock);
>  	rc = radix_tree_insert(&ima_iint_store, (unsigned long)inode, iint);
>  	spin_unlock(&ima_iint_lock);
> +	radix_tree_preload_end();
>  out:
>  	if (rc < 0)
>  		kmem_cache_free(iint_cache, iint);
> 
> -	radix_tree_preload_end();
> -
>  	return rc;
>  }
> 



      reply	other threads:[~2010-02-24 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 10:39 [PATCH] security: fix error return path in ima_inode_alloc Xiaotian Feng
2010-02-24 15:41 ` Mimi Zohar [this message]

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=1267026090.2618.4.camel@localhost.localdomain \
    --to=zohar@linux.vnet.ibm.com \
    --cc=amitarora@in.ibm.com \
    --cc=dfeng@redhat.com \
    --cc=eparis@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=zohar@us.ibm.com \
    /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