[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 22 Feb 2018 11:01:09 +0200
From: Igor Stoppa <igor.stoppa@...wei.com>
To: Kees Cook <keescook@...omium.org>
CC: Matthew Wilcox <willy@...radead.org>, Randy Dunlap
<rdunlap@...radead.org>, Jonathan Corbet <corbet@....net>, Michal Hocko
<mhocko@...nel.org>, Laura Abbott <labbott@...hat.com>, Jerome Glisse
<jglisse@...hat.com>, Christoph Hellwig <hch@...radead.org>, "Christoph
Lameter" <cl@...ux.com>, linux-security-module
<linux-security-module@...r.kernel.org>, Linux-MM <linux-mm@...ck.org>, LKML
<linux-kernel@...r.kernel.org>, Kernel Hardening
<kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH 5/6] Pmalloc: self-test
On 22/02/18 00:24, Kees Cook wrote:
> On Tue, Feb 20, 2018 at 8:40 AM, Igor Stoppa <igor.stoppa@...wei.com> wrote:
[...]
>> sorry for being dense ... are you proposing that I do something to
>> lkdtm_rodata.c ? An example would probably help me understand.
>
> It would likely live in lkdtm_perms.c (or maybe lkdtm_heap.c). Namely,
> use the pmalloc API and then attempt to write to a read-only variable
> in the pmalloc region (to prove that the permission adjustment
> actually happened). Likely a good example is
> lkdtm_WRITE_RO_AFTER_INIT().
ok, thanks for the explanation, I will do it
--
igor
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.
