On Thu, 10 Sep 2015, Paul E. McKenney wrote: > The reason we poked at this was to see if any of SLxB touched the > memory being freed. If none of them touched the memory being freed, > and if that was a policy, then the idiom above would be legal. However, > one of them does touch the memory being freed, so, yes, the above code > needs to be fixed. The one that touches the object has a barrier() before it touches the memory. -- 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>