From: Kees Cook <keescook@chromium.org>
To: "kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: Re: [kernel-hardening] Looking at PAX_MEMORY_SANITIZE
Date: Thu, 17 Dec 2015 12:15:15 -0800 [thread overview]
Message-ID: <CAGXu5jJvgoN+JwCP+ZT==nZap2WFPvCRe02mR6bymSoG-Om6Mw@mail.gmail.com> (raw)
In-Reply-To: <56731502.6050601@labbott.name>
On Thu, Dec 17, 2015 at 12:03 PM, Laura Abbott <laura@labbott.name> wrote:
> On 12/16/15 12:15 PM, Yves-Alexis Perez wrote:
>>
>> On mer., 2015-12-16 at 10:46 -0800, Laura Abbott wrote:
>>>
>>> I'm hoping to post actual patches before I go on vacation for the
>>> holidays next
>>> week. Early feedback is appreciated as well if I missed anything.
>>
>>
>> Note that SANITIZE conflicted with hibernation last time I test, so that's
>> something you might want to test.
>>
>
> That's a good point. I think it's only related to the page allocator which
> I'm
> not focusing on for my first version but I'll still make sure to test before
> I send that out.
It's also easy now to have runtime conflict with hibernation (this is
what kASLR does to avoid a CONFIG conflict with hibernation, via
__setup("kaslr", kaslr_nohibernate_setup)).
-Kees
--
Kees Cook
Chrome OS & Brillo Security
next prev parent reply other threads:[~2015-12-17 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 18:46 [kernel-hardening] Looking at PAX_MEMORY_SANITIZE Laura Abbott
2015-12-16 20:15 ` Yves-Alexis Perez
2015-12-17 20:03 ` Laura Abbott
2015-12-17 20:15 ` Kees Cook [this message]
2015-12-17 1:29 ` Kees Cook
2015-12-17 20:15 ` Laura Abbott
2015-12-17 20:27 ` Kees Cook
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='CAGXu5jJvgoN+JwCP+ZT==nZap2WFPvCRe02mR6bymSoG-Om6Mw@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.