linux-kernel - Re: [RFC PATCH 0/9][V3] Overlayfs SELinux Support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 8 Aug 2016 14:46:51 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Paul Moore <paul@...l-moore.com>
Cc:	James Morris <jmorris@...ei.org>, Vivek Goyal <vgoyal@...hat.com>,
	Stephen Smalley <sds@...ho.nsa.gov>,
	Paul Moore <pmoore@...hat.com>,
	Casey Schaufler <casey@...aufler-ca.com>,
	linux-kernel@...r.kernel.org,
	"linux-unionfs@...r.kernel.org" <linux-unionfs@...r.kernel.org>,
	LSM <linux-security-module@...r.kernel.org>,
	Dan Walsh <dwalsh@...hat.com>,
	David Howells <dhowells@...hat.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	linux-fsdevel@...r.kernel.org
Subject: Re: [RFC PATCH 0/9][V3] Overlayfs SELinux Support

On Fri, Jul 22, 2016 at 5:33 PM, Paul Moore <paul@...l-moore.com> wrote:
> On Thu, Jul 21, 2016 at 7:09 PM, James Morris <jmorris@...ei.org> wrote:
>> On Thu, 21 Jul 2016, Paul Moore wrote:
>>> James, assuming the overlayfs-next branch is pulled during the merge
>>> window, can you rebase your linux-security#next branch to v4.8-rc1
>>> once Linus tags it?
>>
>> Yep.
>
> On Fri, Jul 22, 2016 at 3:05 AM, Miklos Szeredi <miklos@...redi.hu> wrote:
>> On Thu, Jul 21, 2016 at 11:16 PM, Paul Moore <paul@...l-moore.com> wrote:
>>> Hi Vivek,
>>>
>>> These patches look fine to me, thanks for all your hard work and to
>>> everyone who helped review and provide feedback.  I have tagged these
>>> patches for merging into the SELinux next branch after this merge
>>> window.
>>>
>>> Miklos, this patchset depends on patches in your overlayfs-next
>>> branch, I assume you're pushing that branch during the upcoming merge
>>> window?
>>
>> Yes, that's the plan.
>
> Great, thanks.

Base patches are now in v4.8-rc1.

Thanks,
Miklos