From: Paul Moore <pmoore@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov
Subject: [GIT PULL] SELinux patches for 3.14 (part two)
Date: Tue, 07 Jan 2014 14:10:18 -0500 [thread overview]
Message-ID: <3613128.CelVDdi87u@sifl> (raw)
Hi James,
Another pull request for 3.14; this time just a single patch that fixes a
memory leak. The tree below is the exact same as the first 3.14 pull request
with the patch below added. I don't expect any merge problems.
Enjoy,
-Paul
---
The following changes since commit 5e01dc7b26d9f24f39abace5da98ccbd6a5ceb52:
Linux 3.12 (2013-11-03 15:41:51 -0800)
are available in the git repository at:
git://git.infradead.org/users/pcmoore/selinux master
for you to fetch changes up to 8ed814602876bec9bad2649ca17f34b499357a1c:
SELinux: Fix memory leak upon loading policy (2014-01-07 10:21:44 -0500)
----------------------------------------------------------------
Tetsuo Handa (1):
SELinux: Fix memory leak upon loading policy
--
paul moore
security and virtualization @ redhat
next reply other threads:[~2014-01-07 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 19:10 Paul Moore [this message]
2014-01-08 6:16 ` [GIT PULL] SELinux patches for 3.14 (part two) James Morris
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=3613128.CelVDdi87u@sifl \
--to=pmoore@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--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.