Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 21 Sep 2017 11:04:35 -0500 (CDT)
From: Christopher Lameter <>
To: Kees Cook <>
cc: LKML <>, David Windsor <>, 
    Pekka Enberg <>, David Rientjes <>, 
    Joonsoo Kim <>, 
    Andrew Morton <>, Linux-MM <>,, 
    "" <>, 
    Network Development <>, 
    "" <>
Subject: Re: Re: [PATCH v3 03/31] usercopy: Mark kmalloc
 caches as usercopy caches

On Thu, 21 Sep 2017, Kees Cook wrote:

> > So what is the point of this patch?
> The DMA kmalloc caches are not whitelisted:

The DMA kmalloc caches are pretty obsolete and mostly there for obscure


> >>                         kmalloc_dma_caches[i] = create_kmalloc_cache(n,
> >> -                               size, SLAB_CACHE_DMA | flags);
> >> +                               size, SLAB_CACHE_DMA | flags, 0, 0);
> So this is creating the distinction between the kmallocs that go to
> userspace and those that don't. The expectation is that future work
> can start to distinguish between "for userspace" and "only kernel"
> kmalloc allocations, as is already done here for DMA.

The creation of the kmalloc caches in earlier patches already setup the
"whitelisting". Why do it twice?

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.