From: Pirabarlen-Cheenaramen <selven@hackers.mu>
To: selinux@tycho.nsa.gov
Subject: [PATCH] security: hooks : Prevent security to persist in memory (PR #31)
Date: Sun, 23 Apr 2017 02:53:11 +0200 [thread overview]
Message-ID: <20170423005311.GA29693@hackers.mu> (raw)
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 d98550a..9f82908 100644
--- a/security/selinux/hooks.c
+++ b/security/selinux/hooks.c
@@ -4944,7 +4944,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
next reply other threads:[~2017-04-23 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 0:53 Pirabarlen-Cheenaramen [this message]
2017-04-25 21:21 ` [PATCH] security: hooks : Prevent security to persist in memory (PR #31) 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=20170423005311.GA29693@hackers.mu \
--to=selven@hackers.mu \
--cc=selinux@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.