On Sat, 8 Feb 2014, Pekka Enberg wrote: > So to be completely honest, I don't understand what is the race in (A) that > concerns the *memory allocator*. I also don't what the memory allocator can > do in (B) and (C) which look like double-free and use-after-free, > respectively, to me. :-)
Well it seems to be some academic mind game to me. Does an invocation of the allocator have barrier semantics or not? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
