All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Xiaotian Feng <dfeng@redhat.com>
Cc: jmorris@namei.org, eparis@parisplace.org, sds@tycho.nsa.gov,
	paul.moore@hp.com, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] selinux: fix memory leak in sel_make_bools
Date: Thu, 13 Aug 2009 21:36:40 -0500	[thread overview]
Message-ID: <20090814023640.GA21205@us.ibm.com> (raw)
In-Reply-To: <1250215360-20871-1-git-send-email-dfeng@redhat.com>

Quoting Xiaotian Feng (dfeng@redhat.com):
> In sel_make_bools, kernel allocates memory for bool_pending_names[i]
> with security_get_bools. So if we just free bool_pending_names, those
> memories for bool_pending_names[i] will be leaked.
> 
> This patch resolves dozens of following kmemleak report after resuming
> from suspend:
> unreferenced object 0xffff88022e4c7380 (size 32):
>   comm "init", pid 1, jiffies 4294677173
>   backtrace:
>     [<ffffffff810f76b5>] create_object+0x1a2/0x2a9
>     [<ffffffff810f78bb>] kmemleak_alloc+0x26/0x4b
>     [<ffffffff810ef3eb>] __kmalloc+0x18f/0x1b8
>     [<ffffffff811cd511>] security_get_bools+0xd7/0x16f
>     [<ffffffff811c48c0>] sel_write_load+0x12e/0x62b
>     [<ffffffff810f9a39>] vfs_write+0xae/0x10b
>     [<ffffffff810f9b56>] sys_write+0x4a/0x6e
>     [<ffffffff81011b82>] system_call_fastpath+0x16/0x1b
>     [<ffffffffffffffff>] 0xffffffffffffffff
> 
> Signed-off-by: Xiaotian Feng <dfeng@redhat.com>

Acked-by: Serge Hallyn <serue@us.ibm.com>

> ---
>  security/selinux/selinuxfs.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/security/selinux/selinuxfs.c b/security/selinux/selinuxfs.c
> index b4fc506..1a8a1c2 100644
> --- a/security/selinux/selinuxfs.c
> +++ b/security/selinux/selinuxfs.c
> @@ -979,6 +979,8 @@ static int sel_make_bools(void)
>  	u32 sid;
> 
>  	/* remove any existing files */
> +	for (i = 0; i < bool_num; i++)
> +		kfree(bool_pending_names[i]);
>  	kfree(bool_pending_names);
>  	kfree(bool_pending_values);
>  	bool_pending_names = NULL;
> -- 
> 1.6.2.5

  reply	other threads:[~2009-08-14  2:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13  8:26 [PATCH] selinux: fix memory leak in sel_make_bools Xiaotian Feng
2009-08-13 18:55 ` Paul Moore
2009-08-14  2:00   ` Danny Feng
2009-08-14  2:02 ` [PATCH V2] " Xiaotian Feng
2009-08-14  2:36   ` Serge E. Hallyn [this message]
2009-08-14  6:06   ` James Morris
2010-02-08 10:59     ` Xiaotian Feng
2010-02-08 21:24       ` James Morris
  -- strict thread matches above, loose matches on Subject: below --
2009-08-14  4:49 Paul Moore

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=20090814023640.GA21205@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=dfeng@redhat.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul.moore@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.