All of lore.kernel.org
 help / color / mirror / Atom feed
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 fix for 3.16-rcX
Date: Mon, 28 Jul 2014 09:15:27 -0400	[thread overview]
Message-ID: <1466375.GopY4LG4WC@sifl> (raw)
In-Reply-To: <alpine.LRH.2.11.1407170254210.22946@namei.org>

On Thursday, July 17, 2014 02:54:32 AM James Morris wrote:
> On Tue, 15 Jul 2014, Paul Moore wrote:
> > Hi James,
> > 
> > A single fix for the upcoming 3.16 release.  This patch is worth pushing
> > up for 3.16, despite the late stage of the release, because without this
> > patch SELinux systems with the latest version of cryptsetup may not be
> > able to access their encrypted volumes (more details in the patch
> > description) which could prevent the system from booting properly, users
> > accessing their home directories, etc.
> > 
> > The patch is fairly minor and passes the SELinux testsuite.
> 
> Pulled, thanks.

Hi James,

I haven't seen this patch in the last two 3.16-rcX releases from Linus, is 
there a reason this isn't being pushed further up?

-Paul

-- 
paul moore
security and virtualization @ redhat

  reply	other threads:[~2014-07-28 13:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16  2:38 [GIT PULL] SELinux fix for 3.16-rcX Paul Moore
2014-07-16 16:54 ` James Morris
2014-07-28 13:15   ` Paul Moore [this message]
2014-07-28 14:02     ` Paul Moore
2014-07-28 14:38       ` Paul Moore
2014-07-28 15:16 ` Paul Moore
2014-07-29 15:18   ` 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=1466375.GopY4LG4WC@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.