Christoph Lameter wrote: > Well there are architectural problems. We determine the power of two slab > at compile time. The object size information is currently not available in > the binary :=). >
That only applies to allocations with constant sizes. One presumes nobody is explicitly doing kmalloc(0), so we can use a separate runtime-computed-size path to do poisoning. (Which is probably 90% of the problem, since people who kmalloc(sizeof(struct foo)) will generally stay within bounds without too much effort.) J - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
