From: John Johansen <john.johansen@canonical.com>
To: wzt.wzt@gmail.com
Cc: linux-kernel@vger.kernel.org, apparmor@lists.ubuntu.com,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] APPARMOR: Fix memory leak of apparmor_init()
Date: Wed, 10 Nov 2010 08:56:02 -0800 [thread overview]
Message-ID: <4CDACEA2.8010406@canonical.com> (raw)
In-Reply-To: <20101110080515.GA2722@localhost.localdomain>
On 11/10/2010 12:05 AM, wzt.wzt@gmail.com wrote:
> set_init_cxt() allocted sizeof(struct aa_task_cxt) bytes for cxt,
> if register_security() failed, it will cause memory leak.
>
> Signed-off-by: Zhitong Wang <zhitong.wangzt@alibaba-inc.com>
>
yep, thanks again Zhitong
Signed-off-by: John Johansen <john.johansen@canonical.com>
> ---
> security/apparmor/lsm.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/security/apparmor/lsm.c b/security/apparmor/lsm.c
> index cf1de44..b7106f1 100644
> --- a/security/apparmor/lsm.c
> +++ b/security/apparmor/lsm.c
> @@ -922,7 +922,7 @@ static int __init apparmor_init(void)
> error = register_security(&apparmor_ops);
> if (error) {
> AA_ERROR("Unable to register AppArmor\n");
> - goto register_security_out;
> + goto set_init_cxt_out;
> }
>
> /* Report that AppArmor successfully initialized */
> @@ -936,6 +936,9 @@ static int __init apparmor_init(void)
>
> return error;
>
> +set_init_cxt_out:
> + aa_free_task_context(current->real_cred->security);
> +
> register_security_out:
> aa_free_root_ns();
>
> @@ -944,7 +947,6 @@ alloc_out:
>
> apparmor_enabled = 0;
> return error;
> -
> }
>
> security_initcall(apparmor_init);
prev parent reply other threads:[~2010-11-10 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 8:05 [PATCH] APPARMOR: Fix memory leak of apparmor_init() wzt.wzt
2010-11-10 16:56 ` John Johansen [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=4CDACEA2.8010406@canonical.com \
--to=john.johansen@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=wzt.wzt@gmail.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