On Wednesday 27 July 2011, Will Newton wrote:
> >
> > Have you observed this behavior? The interrupt disable/enable should
> > always come with a barrier that should prevent the bitops from
> > leaking out, so I don't see how this causes problems in practice.
>
> Yes, although my arch does not have these barriers. Now I see from
> memory-barriers.txt that lock/unlock are required to implement a
> compiler barrier, sorry for the noise!
Which architectures is this?
Arnd
_______________________________________________
stable mailing list
stable@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/stable
