Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1457761 > unrolled thread

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

Started byMiklos Szeredi <miklos@szeredi.hu>
First post2016-08-08 14:50 +0200
Last post2016-08-08 15:20 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RFC PATCH 0/9][V3] Overlayfs SELinux Support Miklos Szeredi <miklos@szeredi.hu> - 2016-08-08 14:50 +0200
    Re: [RFC PATCH 0/9][V3] Overlayfs SELinux Support Paul Moore <paul@paul-moore.com> - 2016-08-08 15:20 +0200

#1457761 — Re: [RFC PATCH 0/9][V3] Overlayfs SELinux Support

FromMiklos Szeredi <miklos@szeredi.hu>
Date2016-08-08 14:50 +0200
SubjectRe: [RFC PATCH 0/9][V3] Overlayfs SELinux Support
Message-ID<s3Sad-1rV-7@gated-at.bofh.it>
On Fri, Jul 22, 2016 at 5:33 PM, Paul Moore <paul@paul-moore.com> wrote:
> On Thu, Jul 21, 2016 at 7:09 PM, James Morris <jmorris@namei.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@szeredi.hu> wrote:
>> On Thu, Jul 21, 2016 at 11:16 PM, Paul Moore <paul@paul-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

[toc] | [next] | [standalone]


#1457777

FromPaul Moore <paul@paul-moore.com>
Date2016-08-08 15:20 +0200
Message-ID<s3SDf-1Rl-3@gated-at.bofh.it>
In reply to#1457761
On Mon, Aug 8, 2016 at 8:46 AM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> On Fri, Jul 22, 2016 at 5:33 PM, Paul Moore <paul@paul-moore.com> wrote:
>> On Thu, Jul 21, 2016 at 7:09 PM, James Morris <jmorris@namei.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@szeredi.hu> wrote:
>>> On Thu, Jul 21, 2016 at 11:16 PM, Paul Moore <paul@paul-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, I've already pinged James to rebase the linux-security tree,
once he does I'll merge the SELinux/overlayfs patches into the SELinux
next branch.

-- 
paul moore
www.paul-moore.com

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web