Re: [PATCH net 2/3] vhost_net: keep private_data and rx_ring synced

On Fri, Mar 09, 2018 at 02:50:33PM +0800, Jason Wang wrote: > We get pointer ring from the exported sock, this means we should keep > rx_ring and vq->private synced during both vq stop and backend set, > otherwise we may see stale rx_ring. > > Fixes: c67df11f6e480 ("vhost_net: try batch dequing

Re: [PATCH net 2/3] vhost_net: keep private_data and rx_ring synced

On Fri, Mar 09, 2018 at 02:50:33PM +0800, Jason Wang wrote: > We get pointer ring from the exported sock, this means we should keep > rx_ring and vq->private synced during both vq stop and backend set, > otherwise we may see stale rx_ring. > > Fixes: c67df11f6e480 ("vhost_net: try batch dequing

[PATCH net 2/3] vhost_net: keep private_data and rx_ring synced

We get pointer ring from the exported sock, this means we should keep rx_ring and vq->private synced during both vq stop and backend set, otherwise we may see stale rx_ring. Fixes: c67df11f6e480 ("vhost_net: try batch dequing from skb array") Signed-off-by: Michael S. Tsirkin

[PATCH net 2/3] vhost_net: keep private_data and rx_ring synced

We get pointer ring from the exported sock, this means we should keep rx_ring and vq->private synced during both vq stop and backend set, otherwise we may see stale rx_ring. Fixes: c67df11f6e480 ("vhost_net: try batch dequing from skb array") Signed-off-by: Michael S. Tsirkin Signed-off-by: