Currently the xenbus_write() does not handle ring wrapping around
correctly. When ring buffer is almost full and there is not enough
space for next packet (e.g. there is 12 bytes of space left, but the
packet header needs to transmit 16 bytes) the memcpy() goes out of the
ring buffer boundry.
Instead, the part variable should be limited to the space available in
the ring buffer, so the memcpy() can fill up the buffer, update len
variable (to indicate that there is still some data to be copied) and
thereby the xenbus_write() loop can iterate again to finish copying
the remainder of data to the beginning of the ring buffer.
Signed-off-by: Pawel Wieczorkiewicz <wipawel@amazon.de>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
uint32_t prod = ACCESS_ONCE(xb_ring->req_prod);
uint32_t cons = ACCESS_ONCE(xb_ring->req_cons);
- uint32_t used = mask_xenbus_idx(prod - cons);
-
- part = (XENBUS_RING_SIZE - 1) - used;
+ part = (XENBUS_RING_SIZE - 1) - mask_xenbus_idx(prod - cons);
/* No space? Kick xenstored and wait for it to consume some data. */
if ( !part )
}
/* Don't overrun the ring. */
- part = min(part, XENBUS_RING_SIZE - used);
+ part = min(part, XENBUS_RING_SIZE - mask_xenbus_idx(prod));
/* Don't write more than necessary. */
part = min(part, (unsigned int)len);