On Thu, 10 Sep 2015, Dmitry Vyukov wrote: > > It changes the first word of the object after the barrier. The first word > > is used in SLUB as the pointer to the next free object. > > User can also write to this object after it is reallocated. It is > equivalent to kmalloc writing to the object. > And barrier is not the kind of barrier that would make it correct. > So I do not see how it is relevant. This is a compiler barrier so nothing can be moved below that into the code where the freelist pointer is handled. That was the issue from what I heard? -- 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>