[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1801191957160.14056@nuc-kabylake>
Date: Fri, 19 Jan 2018 19:58:38 -0600 (CST)
From: Christopher Lameter <cl@...ux.com>
To: Matthew Wilcox <willy@...radead.org>
cc: Kees Cook <keescook@...omium.org>, linux-mm@...ck.org,
Rik van Riel <riel@...hat.com>, Matthew Garrett <mjg59@...gle.com>,
kernel-hardening@...ts.openwall.com
Subject: Re: kmem_cache_attr (was Re: [PATCH 04/36] usercopy: Prepare for
usercopy whitelisting)
On Wed, 17 Jan 2018, Matthew Wilcox wrote:
> We could put a char * in the kmem_cache which (if not NULL) overrides
> the attr->name? Probably want a helper to replace the endearingly short
> 's->name'. Something like:
>
> #define slab_name(s) s->name ?: s->attr->name
Well I was planning on replacing references to const objects in
kmem_cache_attr throughout the allocators with s->a->xx where a is the
pointer to the attributes in struct kmem_cache. That is also a security
feature if the kmem_cache_attr structures can be placed in readonly
segmenets.
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.
