On 08/11/2016 08:36 AM, Paul Moore wrote:
> On Wed, Aug 10, 2016 at 8:52 AM, Daniel J Walsh wrote:
>> On 08/10/2016 08:32 AM, Paul Moore wrote:
>>> On Wed, Aug 10, 2016 at 5:11 AM, Miklos Szeredi wrote:
On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore
On 08/11/2016 08:36 AM, Paul Moore wrote:
> On Wed, Aug 10, 2016 at 8:52 AM, Daniel J Walsh wrote:
>> On 08/10/2016 08:32 AM, Paul Moore wrote:
>>> On Wed, Aug 10, 2016 at 5:11 AM, Miklos Szeredi wrote:
On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore wrote:
> Okay, I just merged these
On 08/11/2016 08:36 AM, Paul Moore wrote:
> On Wed, Aug 10, 2016 at 8:52 AM, Daniel J Walsh wrote:
>> On 08/10/2016 08:32 AM, Paul Moore wrote:
>>> On Wed, Aug 10, 2016 at 5:11 AM, Miklos Szeredi wrote:
On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore
On 08/11/2016 08:36 AM, Paul Moore wrote:
> On Wed, Aug 10, 2016 at 8:52 AM, Daniel J Walsh wrote:
>> On 08/10/2016 08:32 AM, Paul Moore wrote:
>>> On Wed, Aug 10, 2016 at 5:11 AM, Miklos Szeredi wrote:
On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore wrote:
> Okay, I just merged these
On Wed, Aug 10, 2016 at 8:52 AM, Daniel J Walsh wrote:
> On 08/10/2016 08:32 AM, Paul Moore wrote:
>> On Wed, Aug 10, 2016 at 5:11 AM, Miklos Szeredi wrote:
>>> On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore wrote:
Okay, I just merged
On Wed, Aug 10, 2016 at 8:52 AM, Daniel J Walsh wrote:
> On 08/10/2016 08:32 AM, Paul Moore wrote:
>> On Wed, Aug 10, 2016 at 5:11 AM, Miklos Szeredi wrote:
>>> On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore wrote:
Okay, I just merged these patches into selinux#next. With the
exception
On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore wrote:
> On Thu, Jul 21, 2016 at 5:16 PM, Paul Moore wrote:
>> On Wed, Jul 13, 2016 at 10:44 AM, Vivek Goyal wrote:
>>> Hi All,
>>>
>>> Please find attached the V3 of patches. Changes since
On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore wrote:
> On Thu, Jul 21, 2016 at 5:16 PM, Paul Moore wrote:
>> On Wed, Jul 13, 2016 at 10:44 AM, Vivek Goyal wrote:
>>> Hi All,
>>>
>>> Please find attached the V3 of patches. Changes since V2 are as follows.
>>>
>>> - Fixed the build issue with
On Wed, Aug 10, 2016 at 5:11 AM, Miklos Szeredi wrote:
> On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore wrote:
>> Okay, I just merged these patches into selinux#next. With the
>> exception of some changes to restore the mode argument to
>>
On Wed, Aug 10, 2016 at 5:11 AM, Miklos Szeredi wrote:
> On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore wrote:
>> Okay, I just merged these patches into selinux#next. With the
>> exception of some changes to restore the mode argument to
>> ovl_create_or_link() and to fix some whitespace damage the
On 08/10/2016 08:32 AM, Paul Moore wrote:
> On Wed, Aug 10, 2016 at 5:11 AM, Miklos Szeredi wrote:
>> On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore wrote:
>>> Okay, I just merged these patches into selinux#next. With the
>>> exception of some changes to
On 08/10/2016 08:32 AM, Paul Moore wrote:
> On Wed, Aug 10, 2016 at 5:11 AM, Miklos Szeredi wrote:
>> On Tue, Aug 9, 2016 at 3:19 AM, Paul Moore wrote:
>>> Okay, I just merged these patches into selinux#next. With the
>>> exception of some changes to restore the mode argument to
>>>
On Thu, Jul 21, 2016 at 5:16 PM, Paul Moore wrote:
> On Wed, Jul 13, 2016 at 10:44 AM, Vivek Goyal wrote:
>> Hi All,
>>
>> Please find attached the V3 of patches. Changes since V2 are as follows.
>>
>> - Fixed the build issue with CONFIG_SECURITY=n.
>>
>>
On Thu, Jul 21, 2016 at 5:16 PM, Paul Moore wrote:
> On Wed, Jul 13, 2016 at 10:44 AM, Vivek Goyal wrote:
>> Hi All,
>>
>> Please find attached the V3 of patches. Changes since V2 are as follows.
>>
>> - Fixed the build issue with CONFIG_SECURITY=n.
>>
>> - Dan Walsh was writing more tests for
On Mon, Aug 8, 2016 at 8:46 AM, Miklos Szeredi wrote:
> On Fri, Jul 22, 2016 at 5:33 PM, Paul Moore wrote:
>> On Thu, Jul 21, 2016 at 7:09 PM, James Morris wrote:
>>> On Thu, 21 Jul 2016, Paul Moore wrote:
James, assuming the
On Mon, Aug 8, 2016 at 8:46 AM, Miklos Szeredi wrote:
> On Fri, Jul 22, 2016 at 5:33 PM, Paul Moore wrote:
>> On Thu, Jul 21, 2016 at 7:09 PM, James Morris wrote:
>>> On Thu, 21 Jul 2016, Paul Moore wrote:
James, assuming the overlayfs-next branch is pulled during the merge
window,
On Fri, Jul 22, 2016 at 5:33 PM, Paul Moore wrote:
> On Thu, Jul 21, 2016 at 7:09 PM, James Morris 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
On Fri, Jul 22, 2016 at 5:33 PM, Paul Moore wrote:
> On Thu, Jul 21, 2016 at 7:09 PM, James Morris 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
>>>
On Thu, Jul 21, 2016 at 7:09 PM, James Morris 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,
On Thu, Jul 21, 2016 at 7:09 PM, James Morris 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
On Thu, Jul 21, 2016 at 11:16 PM, Paul Moore 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
On Thu, Jul 21, 2016 at 11:16 PM, Paul Moore 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.
>
>
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.
--
James Morris
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.
--
James Morris
On Wed, Jul 13, 2016 at 10:44 AM, Vivek Goyal wrote:
> Hi All,
>
> Please find attached the V3 of patches. Changes since V2 are as follows.
>
> - Fixed the build issue with CONFIG_SECURITY=n.
>
> - Dan Walsh was writing more tests for selinux-testsuite and noted couple
> of
On Wed, Jul 13, 2016 at 10:44 AM, Vivek Goyal wrote:
> Hi All,
>
> Please find attached the V3 of patches. Changes since V2 are as follows.
>
> - Fixed the build issue with CONFIG_SECURITY=n.
>
> - Dan Walsh was writing more tests for selinux-testsuite and noted couple
> of issues. I have fixed
Hi All,
Please find attached the V3 of patches. Changes since V2 are as follows.
- Fixed the build issue with CONFIG_SECURITY=n.
- Dan Walsh was writing more tests for selinux-testsuite and noted couple
of issues. I have fixed those issues and added two more patches in series.
1. We are
Hi All,
Please find attached the V3 of patches. Changes since V2 are as follows.
- Fixed the build issue with CONFIG_SECURITY=n.
- Dan Walsh was writing more tests for selinux-testsuite and noted couple
of issues. I have fixed those issues and added two more patches in series.
1. We are
28 matches
Mail list logo