Stefano Garzarella
2019-Apr-05 09:36 UTC
[PATCH RFC 2/4] vhost/vsock: split packets to send using multiple buffers
On Fri, Apr 05, 2019 at 09:13:56AM +0100, Stefan Hajnoczi wrote:> On Thu, Apr 04, 2019 at 12:58:36PM +0200, Stefano Garzarella wrote: > > @@ -139,8 +139,18 @@ vhost_transport_do_send_pkt(struct vhost_vsock *vsock, > > break; > > } > > > > - len = iov_length(&vq->iov[out], in); > > - iov_iter_init(&iov_iter, READ, &vq->iov[out], in, len); > > + payload_len = pkt->len - pkt->off; > > + iov_len = iov_length(&vq->iov[out], in); > > + iov_iter_init(&iov_iter, READ, &vq->iov[out], in, iov_len); > > + > > + /* If the packet is greater than the space available in the > > + * buffer, we split it using multiple buffers. > > + */ > > + if (payload_len > iov_len - sizeof(pkt->hdr)) > > Integer underflow. iov_len is controlled by the guest and therefore > untrusted. Please validate iov_len before assuming it's larger than > sizeof(pkt->hdr). >Okay, I'll do it!> > - vhost_add_used(vq, head, sizeof(pkt->hdr) + pkt->len); > > + vhost_add_used(vq, head, sizeof(pkt->hdr) + payload_len); > > added = true; > > > > + pkt->off += payload_len; > > + > > + /* If we didn't send all the payload we can requeue the packet > > + * to send it with the next available buffer. > > + */ > > + if (pkt->off < pkt->len) { > > + spin_lock_bh(&vsock->send_pkt_list_lock); > > + list_add(&pkt->list, &vsock->send_pkt_list); > > + spin_unlock_bh(&vsock->send_pkt_list_lock); > > + continue; > > The virtio_transport_deliver_tap_pkt() call is skipped. Packet capture > should see the exact packets that are delivered. I think this patch > will present one large packet instead of several smaller packets that > were actually delivered.I'll modify virtio_transport_build_skb() to take care of pkt->off and reading the payload size from the virtio_vsock_hdr. Otherwise, should I introduce another field in virtio_vsock_pkt to store the payload size? Thanks, Stefano
Stefan Hajnoczi
2019-Apr-08 09:28 UTC
[PATCH RFC 2/4] vhost/vsock: split packets to send using multiple buffers
On Fri, Apr 05, 2019 at 11:36:08AM +0200, Stefano Garzarella wrote:> On Fri, Apr 05, 2019 at 09:13:56AM +0100, Stefan Hajnoczi wrote: > > On Thu, Apr 04, 2019 at 12:58:36PM +0200, Stefano Garzarella wrote: > > > - vhost_add_used(vq, head, sizeof(pkt->hdr) + pkt->len); > > > + vhost_add_used(vq, head, sizeof(pkt->hdr) + payload_len); > > > added = true; > > > > > > + pkt->off += payload_len; > > > + > > > + /* If we didn't send all the payload we can requeue the packet > > > + * to send it with the next available buffer. > > > + */ > > > + if (pkt->off < pkt->len) { > > > + spin_lock_bh(&vsock->send_pkt_list_lock); > > > + list_add(&pkt->list, &vsock->send_pkt_list); > > > + spin_unlock_bh(&vsock->send_pkt_list_lock); > > > + continue; > > > > The virtio_transport_deliver_tap_pkt() call is skipped. Packet capture > > should see the exact packets that are delivered. I think this patch > > will present one large packet instead of several smaller packets that > > were actually delivered. > > I'll modify virtio_transport_build_skb() to take care of pkt->off > and reading the payload size from the virtio_vsock_hdr. > Otherwise, should I introduce another field in virtio_vsock_pkt to store > the payload size?I don't remember the details but I trust you'll pick a good way of doing it. Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: not available URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20190408/142f66c9/attachment-0001.sig>
Possibly Parallel Threads
- [PATCH RFC 2/4] vhost/vsock: split packets to send using multiple buffers
- [PATCH RFC 2/4] vhost/vsock: split packets to send using multiple buffers
- [PATCH v4 4/5] vhost/vsock: split packets to send using multiple buffers
- [PATCH v4 4/5] vhost/vsock: split packets to send using multiple buffers
- [PATCH v4 4/5] vhost/vsock: split packets to send using multiple buffers