Re: [PATCH] malloc: Use correct C11 atomics for fastbin

[Florian Weimer <fweimer@redhat.com>]

* Wilco Dijkstra:

> Fix memory ordering issues in the fastbin implementation: in REMOVE_FB the
> next pointer is read before any MO synchronization, however in the C11 atomic
> model this is only correct after a load acquire. Refactor the fastbin code
> and add a dedicated fastbin_push/pop implementation. The number of acquire
> or release atomics remains the same, and the new functions are inlined, so
> performance is unaffected.
>
> Passes regress, OK for commit?

Did you actually observe any problems resulting from this?  We
previously concluded that the dependency chain would mae this valid
(outside the C11 memory model).

Thanks,
Florian