[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJDUgPDYduR0pZ14vNO2pXpFgwEG6SZhPOjyUQBt+Oi_g@mail.gmail.com>
Date: Wed, 1 Mar 2017 14:58:29 -0800
From: Kees Cook <keescook@...omium.org>
To: PaX Team <pageexec@...email.hu>
Cc: Brad Spengler <spender@...ecurity.net>, Mark Rutland <mark.rutland@....com>,
Hoeun Ryu <hoeun.ryu@...il.com>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH] PCI: Fix typo in pax_open/close_kernel wrapping
On Wed, Mar 1, 2017 at 2:46 PM, Kees Cook <keescook@...omium.org> wrote:
> On Wed, Mar 1, 2017 at 1:45 PM, PaX Team <pageexec@...email.hu> wrote:
>> On 1 Mar 2017 at 12:33, Kees Cook wrote:
>>
>>> This fixes a mistaken double-open in PaX's constification coverage of
>>> cpcihp_zt5550.
>>
>> patch complains with:
>>
>> checking file drivers/pci/hotplug/cpcihp_zt5550.c
>> Reversed (or previously applied) patch detected! Assume -R? [n]
>>
>> are you sure you're looking at a recent tree?
>
> I guess not! Sorry for the noise. This was from pax-linux-4.9.9-test3.patch.
Actually, it looks like it's an error in the grsecurity merge of PaX.
The mistake is present in the current grsecurity testing patch:
https://grsecurity.net/test/grsecurity-3.1-4.9.13-201702270729.patch
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
