[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b75b5903-0177-8ad9-5c2b-fc63438fb5f2@huawei.com>
Date: Sat, 3 Feb 2018 21:57:13 +0200
From: Igor Stoppa <igor.stoppa@...wei.com>
To: Christopher Lameter <cl@...ux.com>, Matthew Wilcox <willy@...radead.org>,
Boris Lukashev <blukashev@...pervictus.com>
CC: Jann Horn <jannh@...gle.com>, <jglisse@...hat.com>, Kees Cook
<keescook@...omium.org>, Michal Hocko <mhocko@...nel.org>, Laura Abbott
<labbott@...hat.com>, Christoph Hellwig <hch@...radead.org>,
<linux-security-module@...r.kernel.org>, <linux-mm@...ck.org>, kernel list
<linux-kernel@...r.kernel.org>, Kernel Hardening
<kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH 4/6] Protectable Memory
>> On Thu, 25 Jan 2018, Matthew Wilcox wrote:
>>> It's worth having a discussion about whether we want the pmalloc API
>>> or whether we want a slab-based API.
I'd love to have some feedback specifically about the API.
I have also some idea about userspace and how to extend the pmalloc
concept to it:
http://www.openwall.com/lists/kernel-hardening/2018/01/30/20
I'll be AFK intermittently for about 2 weeks, so i might not be able to
reply immediately, but from my perspective this would be just the
beginning of a broader hardening of both kernel and userspace that I'd
like to pursue.
--
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.
