[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170131071935.3e34cdd6@kaiwan-T460>
Date: Tue, 31 Jan 2017 07:19:35 +0530
From: Kaiwan N Billimoria <kaiwan@...wantech.com>
To: Laura Abbott <labbott@...hat.com>, kernel-hardening@...ts.openwall.com
Cc: keescook@...omium.org, labbott@...hat.com
Subject: Re: Merge in PAX_MEMORY_SANITIZE work from grsec
to linux-next
Apologies for the delayed response!
>On Wed, 18 Jan 2017 11:44:47 -0800
>Laura Abbott <labbott@...hat.com> wrote:
> This is roughly the work I did before
> (http://www.openwall.com/lists/kernel-hardening/2015/12/22/1)
Yes Laura, indeed it _is_ your code that I merged into linux-next, just
attempting to move forward. Thanks :)
> From that discussion, the conclusion is that we need to
> use the existing slab_debug infrastructure to do sanitization.
> The part in mm/page_alloc.c has been turned into a separate
> Kconfig.
Ok, so, I'll attempt working on going down this path, also taking into
account what you mentioned Kees.. will take it a step at a time though!
> As Kees mentioned, a good task would be to create a new Kconfig
> (CONFIG_MEMORY_SANITIZE for example) that will turn on both
> CONFIG_DEBUG_PAGEALLOC (the equivalent of CONFIG_PAX_MEMORY_SANITIZE)
> and also turn on slab poisoning.
>
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.
