From: Paul Moore <pmoore@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [GIT PULL] SELinux fixes for 3.13 (part three)
Date: Mon, 23 Dec 2013 16:19:39 -0500 [thread overview]
Message-ID: <1678336.HYoZuQ9LME@sifl> (raw)
In-Reply-To: <3917996.DVt9Qik8HG@sifl>
On Wednesday, December 18, 2013 05:04:26 PM Paul Moore wrote:
> Hi James,
>
> Two more small patches for 3.13-rcX. Both fix long standing issues, and
> both should be very uncontroversial. FYI, I've left my previous sent
> 3.13-rcX fixes in the tree below, including the revert patch that Linus did
> himself before it could flow from the SELinux tree.
>
> Enjoy,
> -Paul
These two patches really should go into the 3.13 release, the patch from Chad
is particularly important. Any hope of pushing this to Linus soon?
> ---
> The following changes are available in the git repository at:
>
> git://git.infradead.org/users/pcmoore/selinux_fixes master
>
> for you to fetch changes up to 67439a11ae99e19cfdc3a8f6d7fde24e07e34acb:
>
> selinux: selinux_setprocattr()->ptrace_parent() needs rcu_read_lock()
> (2013-12-16 16:16:08 -0500)
>
> ----------------------------------------------------------------
> Chad Hanson (1):
> selinux: fix broken peer recv check
>
> Oleg Nesterov (1):
> selinux: selinux_setprocattr()->ptrace_parent() needs rcu_read_lock()
>
> security/selinux/hooks.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
--
paul moore
security and virtualization @ redhat
next prev parent reply other threads:[~2013-12-23 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 22:04 [GIT PULL] SELinux fixes for 3.13 (part three) Paul Moore
2013-12-23 21:19 ` Paul Moore [this message]
2013-12-23 22:34 ` James Morris
2013-12-23 22:51 ` Paul Moore
2013-12-24 4:03 ` Eric Paris
2013-12-24 6:48 ` 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=1678336.HYoZuQ9LME@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.