On Fri, May 27, 2016 at 7:30 PM, Christoph Lameter wrote:
> On Fri, 27 May 2016, Alexander Potapenko wrote:
>
>> It's reasonable to rely on the fact that for every page allocated for a
>> kmem_cache the |slab_cache| field points to that cache. Without that it's
>> hard to figure
On Fri, May 27, 2016 at 7:30 PM, Christoph Lameter wrote:
> On Fri, 27 May 2016, Alexander Potapenko wrote:
>
>> It's reasonable to rely on the fact that for every page allocated for a
>> kmem_cache the |slab_cache| field points to that cache. Without that it's
>> hard to figure out which cache
On Fri, 27 May 2016, Alexander Potapenko wrote:
> It's reasonable to rely on the fact that for every page allocated for a
> kmem_cache the |slab_cache| field points to that cache. Without that it's
> hard to figure out which cache does an allocated object belong to.
The flags are set only in the
On Fri, 27 May 2016, Alexander Potapenko wrote:
> It's reasonable to rely on the fact that for every page allocated for a
> kmem_cache the |slab_cache| field points to that cache. Without that it's
> hard to figure out which cache does an allocated object belong to.
The flags are set only in the
It's reasonable to rely on the fact that for every page allocated for a
kmem_cache the |slab_cache| field points to that cache. Without that it's
hard to figure out which cache does an allocated object belong to.
Fixes: 55834c59098d0c5a97b0f324 ("mm: kasan: initial memory quarantine
It's reasonable to rely on the fact that for every page allocated for a
kmem_cache the |slab_cache| field points to that cache. Without that it's
hard to figure out which cache does an allocated object belong to.
Fixes: 55834c59098d0c5a97b0f324 ("mm: kasan: initial memory quarantine
6 matches
Mail list logo