>>> On 30.04.18 at 23:54, <marma...@invisiblethingslab.com> wrote: > Using RING_GET_RESPONSE() on a shared ring is easy to use incorrectly > (i.e., by not considering that the other end may alter the data in the > shared ring while it is being inspected). Safe usage of a response > generally requires taking a local copy. > > Provide a RING_COPY_RESPONSE() macro to use instead of > RING_GET_RESPONSE() and an open-coded memcpy(). This takes care of > ensuring that the copy is done correctly regardless of any possible > compiler optimizations. > > Use a volatile source to prevent the compiler from reordering or > omitting the copy. > > This is complementary to XSA155. > > Signed-off-by: Marek Marczykowski-Górecki <marma...@invisiblethingslab.com>
Please don't forget to Cc maintainers of files you change. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
