From: "PaX Team" <pageexec@freemail.hu>
To: Kees Cook <keescook@chromium.org>
Cc: Brad Spengler <spender@grsecurity.net>,
Mark Rutland <mark.rutland@arm.com>,
Hoeun Ryu <hoeun.ryu@gmail.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: [kernel-hardening] Re: [PATCH] PCI: Fix typo in pax_open/close_kernel wrapping
Date: Thu, 02 Mar 2017 00:14:51 +0100 [thread overview]
Message-ID: <58B755EB.29911.B909EA3@pageexec.freemail.hu> (raw)
In-Reply-To: <CAGXu5jJDUgPDYduR0pZ14vNO2pXpFgwEG6SZhPOjyUQBt+Oi_g@mail.gmail.com>
On 1 Mar 2017 at 14:58, Kees Cook wrote:
> >> 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
he doesn't take such low priority fixes immediately (i found this regression
myself only a few days ago during the 4.10 port) but collects a few more of
them before making a new release.
prev parent reply other threads:[~2017-03-01 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 20:33 [kernel-hardening] [PATCH] PCI: Fix typo in pax_open/close_kernel wrapping Kees Cook
2017-03-01 21:45 ` [kernel-hardening] " PaX Team
2017-03-01 22:46 ` Kees Cook
2017-03-01 22:58 ` Kees Cook
2017-03-01 23:14 ` PaX Team [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58B755EB.29911.B909EA3@pageexec.freemail.hu \
--to=pageexec@freemail.hu \
--cc=hoeun.ryu@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=mark.rutland@arm.com \
--cc=spender@grsecurity.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox