On Mon, Apr 8, 2019 at 9:43 AM Laura Abbott <labbott@xxxxxxxxxx> wrote: > I've looked at doing something similar in the past (failing to find > the thread this morning...) and while this will work, it has pretty > serious performance issues. It's not actually the poisoning which > is expensive but that turning on debugging removes the cpu slab > which has significant performance penalties. > > I'd rather go back to the proposal of just poisoning the slab > at alloc/free without using SLAB_POISON. I still agree this would make the most sense. Fundamentally it's not a debugging feature. -- Kees Cook