From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from goalie.tycho.ncsc.mil (goalie [144.51.242.250]) by tarius.tycho.ncsc.mil (8.14.4/8.14.4) with ESMTP id s6SE2slR007456 for ; Mon, 28 Jul 2014 10:02:54 -0400 From: Paul Moore To: James Morris Subject: Re: [GIT PULL] SELinux fix for 3.16-rcX Date: Mon, 28 Jul 2014 10:02:54 -0400 Message-ID: <5414093.IMbuFni8DV@sifl> In-Reply-To: <1466375.GopY4LG4WC@sifl> References: <2092564.8lACVUTXtn@sifl> <1466375.GopY4LG4WC@sifl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov List-Id: "Security-Enhanced Linux \(SELinux\) mailing list" List-Post: List-Help: On Monday, July 28, 2014 09:15:27 AM Paul Moore wrote: > 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? B'ah, nevermind. Probably best to hold on this I guess, I just got one report of a problem that *may* be related. -- paul moore security and virtualization @ redhat