Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 27 Jan 2016 00:21:35 +0900
From: Joonsoo Kim <>
To: Christoph Lameter <>
Cc: Joonsoo Kim <>, Laura Abbott <>, 
	Pekka Enberg <>, David Rientjes <>, 
	Andrew Morton <>, 
	Linux Memory Management List <>, LKML <>,, Kees Cook <>
Subject: Re: [RFC][PATCH 0/3] Speed up SLUB poisoning + disable checks

2016-01-27 0:01 GMT+09:00 Christoph Lameter <>:
> On Tue, 26 Jan 2016, Joonsoo Kim wrote:
>> I doesn't follow up that discussion, but, I think that reusing
>> SLAB_POISON for slab sanitization needs more changes. I assume that
>> completeness and performance is matter for slab sanitization.
>> 1) SLAB_POISON isn't applied to specific kmem_cache which has
>> constructor or SLAB_DESTROY_BY_RCU flag. For debug, it's not necessary
>> to be applied, but, for slab sanitization, it is better to apply it to
>> all caches.
> Those slabs can be legitimately accessed after the objects were freed. You
> cannot sanitize nor poison.

Oops... you are right. I misunderstand what SLAB_DESTROY_BY_RCU is.
Now, it's clear to me.


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.