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, 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>