[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <774d9fc1-4caf-a6c9-3693-a90b5b954645@huawei.com>
Date: Mon, 10 Jul 2017 18:15:53 +0300
From: Igor Stoppa <igor.stoppa@...wei.com>
To: Jerome Glisse <jglisse@...hat.com>
CC: <keescook@...omium.org>, <mhocko@...nel.org>, <jmorris@...ei.org>,
<labbott@...hat.com>, <hch@...radead.org>,
<penguin-kernel@...ove.SAKURA.ne.jp>, <paul@...l-moore.com>,
<sds@...ho.nsa.gov>, <casey@...aufler-ca.com>,
<linux-security-module@...r.kernel.org>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, <kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH 1/3] Protectable memory support
On 07/07/17 21:48, Jerome Glisse wrote:
> I believe there is enough unuse field that for vmalloc pages that
> you should find one you can use. Just add some documentation in
> mm_types.h so people are aware of alternate use for the field you
> are using.
I ended up using page->private and the corresponding bit.
Because page-private is an opaque field, specifically reserved for the
allocator, I think it should not be necessary to modify mm_types.h
The reworked patch is here:
https://marc.info/?l=linux-mm&m=149969928920772&w=2
--
thanks, 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.
