On Tue, 5 Jan 2016, Laura Abbott wrote: > It's not the poisoning per se that's incompatible, it's how the poisoning is > set up. At least for slub, the current poisoning is part of SLUB_DEBUG which > enables other consistency checks on the allocator. Trying to pull out just > the poisoning for use when SLUB_DEBUG isn't on would result in roughly what > would be here anyway. I looked at trying to reuse some of the existing > poisoning > and came to the conclusion it was less intrusive to the allocator to keep it > separate. SLUB_DEBUG does *not* enable any debugging features. It builds the logic for debugging into the kernel but does not activate it. CONFIG_SLUB_DEBUG is set for production kernels. The poisoning is build in by default into any recent linux kernel out there. You can enable poisoning selectively (and no other debug feature) by specifying slub_debug=P on the Linux kernel command line right now. There is a SLAB_POISON flag for each kmem_cache that can be set to *only* enable poisoning and nothing else from code. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>