another guest-to-host escape because of switch() on shared memory without proper "volatile" markerhttps://twitter.com/renorobertr/status/1034366945678639104 …
linux uses volatile reads inside rcu_dereference() for locklessly reading pointers, and the only architecture on which that macro includes a barrier is alpha (because that's the only arch that can reorder dependent loads).
-
-
the write side (rcu_assign_pointer()) uses only a compiler barrier on X86, and a store-release instruction on ARM64
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.