On Thu, Mar 26, 2015 at 10:24 AM, Christian Borntraeger
<borntraeger@xxxxxxxxxx> wrote:
>
> Oh I just added that check back then because some guy named
> Linus suggested something like that ;-)
Yes, my bad.
In my defense, that was when we were talking about ACCESS_ONCE()
causing bugs with gcc due to the blind use of "volatile" that it turns
out gcc doesn't necessarily like.
With the memcpy fallback (and the simpler "scalar pointer copy by
hand"), I think READ_ONCE() (and WRITE_ONCE()) are safe.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
