From: Kaiwan N Billimoria <kaiwan@kaiwantech.com>
To: Laura Abbott <labbott@redhat.com>, kernel-hardening@lists.openwall.com
Cc: keescook@chromium.org
Subject: Re: [kernel-hardening] Merge in PAX_MEMORY_SANITIZE work from grsec to linux-next
Date: Tue, 31 Jan 2017 07:19:35 +0530 [thread overview]
Message-ID: <20170131071935.3e34cdd6@kaiwan-T460> (raw)
In-Reply-To: <90224a2d-2bfc-8c1e-1f2c-ca5bfbdb4879@redhat.com>
Apologies for the delayed response!
>On Wed, 18 Jan 2017 11:44:47 -0800
>Laura Abbott <labbott@redhat.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.
>
next prev parent reply other threads:[~2017-01-31 1:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 4:21 [kernel-hardening] Merge in PAX_MEMORY_SANITIZE work from grsec to linux-next Kaiwan N Billimoria
2017-01-18 19:44 ` Laura Abbott
2017-01-31 1:49 ` Kaiwan N Billimoria [this message]
2017-02-03 4:49 ` Kaiwan N Billimoria
2017-02-04 0:23 ` Kees Cook
2017-02-04 3:12 ` Kaiwan N Billimoria
2017-02-09 3:37 ` Kaiwan N Billimoria
2017-02-13 11:42 ` Kaiwan N Billimoria
2017-02-13 17:28 ` Kees Cook
2017-02-14 3:01 ` Kaiwan N Billimoria
2017-02-14 17:19 ` Kees Cook
2017-02-15 7:27 ` Kaiwan N Billimoria
2017-02-15 20:30 ` Kees Cook
2017-02-17 3:18 ` Kaiwan N Billimoria
2017-02-21 23:26 ` Kees Cook
2017-02-24 9:38 ` Kaiwan N Billimoria
2017-02-14 8:04 ` Kaiwan N Billimoria
2017-02-14 16:19 ` Mark Rutland
2017-02-14 16:33 ` Kaiwan N Billimoria
2017-01-19 0:54 ` 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=20170131071935.3e34cdd6@kaiwan-T460 \
--to=kaiwan@kaiwantech.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox