From: selven@hackers.mu (Pirabarlen Cheenaramen)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] selinux: hooks: security content must be properly cleared
Date: Sun, 23 Apr 2017 08:48:32 +0200 [thread overview]
Message-ID: <20170423064832.GA4042@hackers.mu> (raw)
In-Reply-To: <20170423000551.GA25768@hackers.mu>
Please disregard this patch.
On Sun, Apr 23, 2017 at 02:05:51AM +0200, Pirabarlen-Cheenaramen wrote:
> Signed-off-by: Pirabarlen-Cheenaramen <selven@hackers.mu>
> ---
> security/selinux/hooks.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
> index e67a526..ef3fa80 100644
> --- a/security/selinux/hooks.c
> +++ b/security/selinux/hooks.c
> @@ -4969,7 +4969,7 @@ static int selinux_tun_dev_alloc_security(void **security)
>
> static void selinux_tun_dev_free_security(void *security)
> {
> - kfree(security);
> + kzfree(security);
> }
>
> static int selinux_tun_dev_create(void)
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-04-23 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 0:05 [PATCH] selinux: hooks: security content must be properly cleared Pirabarlen-Cheenaramen
2017-04-23 6:48 ` Pirabarlen Cheenaramen [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=20170423064832.GA4042@hackers.mu \
--to=selven@hackers.mu \
--cc=linux-security-module@vger.kernel.org \
/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.