From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: Mimi Zohar <zohar@us.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Serge Hallyn <serue@us.ibm.com>, James Morris <jmorris@namei.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] integrity: fix IMA inode leak
Date: Sun, 07 Jun 2009 02:07:30 -0400 [thread overview]
Message-ID: <1244354850.3963.21.camel@dyn9002018117.watson.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906062109580.8365@sister.anvils>
On Sat, 2009-06-06 at 21:18 +0100, Hugh Dickins wrote:
> CONFIG_IMA=y inode activity leaks iint_cache and radix_tree_node objects
> until the system runs out of memory. Nowhere is calling ima_inode_free()
> a.k.a. ima_iint_delete(). Fix that by calling it from destroy_inode().
>
> Signed-off-by: Hugh Dickins <hugh.dickins@tiscali.co.uk>
This call was accidentally dropped in the conversion from
using the LIM hooks to embedding the IMA calls directly. I'm
really sorry.
Acked-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
> ---
>
> fs/inode.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- 2.6.30-rc8/fs/inode.c 2009-05-16 10:26:15.000000000 +0100
> +++ linux/fs/inode.c 2009-06-06 17:41:21.000000000 +0100
> @@ -219,6 +219,7 @@ static struct inode *alloc_inode(struct
> void destroy_inode(struct inode *inode)
> {
> BUG_ON(inode_has_buffers(inode));
> + ima_inode_free(inode);
> security_inode_free(inode);
> if (inode->i_sb->s_op->destroy_inode)
> inode->i_sb->s_op->destroy_inode(inode);
prev parent reply other threads:[~2009-06-07 6:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 20:18 Hugh Dickins
2009-06-06 21:18 ` Linus Torvalds
2009-06-06 21:35 ` Linus Torvalds
2009-06-06 22:29 ` Hugh Dickins
2009-06-07 6:08 ` Mimi Zohar
2009-06-07 23:09 ` Linus Torvalds
2009-06-08 12:28 ` Mimi Zohar
2009-06-08 16:15 ` Linus Torvalds
2009-06-08 18:44 ` Mimi Zohar
2009-06-08 23:16 ` James Morris
2009-06-09 2:56 ` Mimi Zohar
2009-06-09 3:42 ` Casey Schaufler
2009-06-07 6:07 ` 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=1244354850.3963.21.camel@dyn9002018117.watson.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®