From mboxrd@z Thu Jan  1 00:00:00 1970
From: jglisse@redhat.com (Jerome Glisse)
Date: Fri, 7 Jul 2017 14:48:44 -0400
Subject: [PATCH 1/3] Protectable memory support
In-Reply-To: <1665fd00-5908-2399-577d-1972c7d1c63b@huawei.com>
References: <20170705134628.3803-1-igor.stoppa@huawei.com>
	<20170705134628.3803-2-igor.stoppa@huawei.com>
	<20170706162742.GA2919@redhat.com>
	<1665fd00-5908-2399-577d-1972c7d1c63b@huawei.com>
Message-ID: <20170707184843.GA3113@redhat.com>
To: linux-security-module@vger.kernel.org
List-Id: linux-security-module.vger.kernel.org

On Fri, Jul 07, 2017 at 11:42:09AM +0300, Igor Stoppa wrote:
> On 06/07/17 19:27, Jerome Glisse wrote:
> > On Wed, Jul 05, 2017 at 04:46:26PM +0300, Igor Stoppa wrote:

[...]

> > Yet another way is to use some of the free struct page fields ie
> > when a page is allocated for vmalloc i think most of struct page
> > fields are unuse (mapping, index, lru, ...). It would be better
> > to use those rather than adding a page flag.
> 
> Like introducing an unnamed union? Some sort of vmalloc_page_subtype?
> If that is what you are proposing, I agree that it would work in a
> similar fashion as what I have now, but without introducing the overhead
> of the extra page flag.

No need to introduce unamed union or anything. Just use one of the
existing field for install you can make page->mapping point to the
pmalloc pool structure. Or you can store a unique key value.

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.

J?r?me
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html