From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
anthony.perard@citrix.com,
Stefano Stabellini <stefano.stabellini@xilinx.com>,
groug@kaod.org
Subject: Re: [PATCH] 9p: init_in_iov_from_pdu can truncate the size
Date: Thu, 19 Dec 2019 18:08:26 +0100 [thread overview]
Message-ID: <2734053.qHGH40kZ6z@silver> (raw)
In-Reply-To: <20191219004251.23763-1-sstabellini@kernel.org>
On Donnerstag, 19. Dezember 2019 01:42:51 CET Stefano Stabellini wrote:
> From: Stefano Stabellini <stefano.stabellini@xilinx.com>
>
> init_in_iov_from_pdu might not be able to allocate the full buffer size
> requested, which comes from the client and could be larger than the
> transport has available at the time of the request. Specifically, this
> can happen with read operations, with the client requesting a read up to
> the max allowed, which might be more than the transport has available at
> the time.
I haven't looked thoroughly at this yet, but that's about addressing a
temporary, not a permanent transport buffer size limitation, right? Because if
it was a permanent one, then probably an adjusted (lowered) msize should be
returned on R_version response to client as well.
I wonder why I never triggered this issue, because I was experimenting with
huge msize values for 9pfs performance checks. Was there anything specific to
trigger this issue?
> Today the implementation of init_in_iov_from_pdu throws an error, both
> Xen and Virtio.
>
> Instead, change the V9fsTransport interface so that the size becomes a
> pointer and can be limited by the implementation of
> init_in_iov_from_pdu.
>
> Change both the Xen and Virtio implementations to set the size to the
> size of the buffer they managed to allocate, instead of throwing an
> error.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@xilinx.com>
> CC: groug@kaod.org
> CC: anthony.perard@citrix.com
> ---
> hw/9pfs/9p.c | 22 +++++++++++++++-------
> hw/9pfs/9p.h | 2 +-
> hw/9pfs/virtio-9p-device.c | 10 +++-------
> hw/9pfs/xen-9p-backend.c | 12 ++++--------
> 4 files changed, 23 insertions(+), 23 deletions(-)
>
> diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
> index bdf7919abf..d6c89ce608 100644
> --- a/hw/9pfs/9p.c
> +++ b/hw/9pfs/9p.c
> @@ -1682,22 +1682,30 @@ out_nofid:
> * with qemu_iovec_destroy().
> */
> static void v9fs_init_qiov_from_pdu(QEMUIOVector *qiov, V9fsPDU *pdu,
> - size_t skip, size_t size,
> + size_t skip, size_t *size,
> bool is_write)
> {
> QEMUIOVector elem;
> struct iovec *iov;
> unsigned int niov;
> + size_t alloc_size = *size + skip;
>
> if (is_write) {
> - pdu->s->transport->init_out_iov_from_pdu(pdu, &iov, &niov, size +
> skip); + pdu->s->transport->init_out_iov_from_pdu(pdu, &iov, &niov,
> alloc_size); } else {
> - pdu->s->transport->init_in_iov_from_pdu(pdu, &iov, &niov, size +
> skip); + pdu->s->transport->init_in_iov_from_pdu(pdu, &iov, &niov,
> &alloc_size); + }
> +
> + if (alloc_size < skip)
> + {
> + *size = 0;
> + } else {
> + *size = alloc_size - skip;
> }
>
Code style nitpicking:
ERROR: that open brace { should be on the previous line
#56: FILE: hw/9pfs/9p.c:1699:
+ if (alloc_size < skip)
+ {
>
> static int v9fs_xattr_read(V9fsState *s, V9fsPDU *pdu, V9fsFidState *fidp,
> @@ -1722,7 +1730,7 @@ static int v9fs_xattr_read(V9fsState *s, V9fsPDU *pdu,
> V9fsFidState *fidp, }
> offset += err;
>
> - v9fs_init_qiov_from_pdu(&qiov_full, pdu, offset, read_count, false);
> + v9fs_init_qiov_from_pdu(&qiov_full, pdu, offset, &read_count, false);
> err = v9fs_pack(qiov_full.iov, qiov_full.niov, 0,
> ((char *)fidp->fs.xattr.value) + off,
> read_count);
> @@ -1852,7 +1860,7 @@ static void coroutine_fn v9fs_read(void *opaque)
> QEMUIOVector qiov;
> int32_t len;
>
> - v9fs_init_qiov_from_pdu(&qiov_full, pdu, offset + 4, max_count,
> false); + v9fs_init_qiov_from_pdu(&qiov_full, pdu, offset + 4,
> &max_count, false); qemu_iovec_init(&qiov, qiov_full.niov);
> do {
> qemu_iovec_reset(&qiov);
> @@ -2085,7 +2093,7 @@ static void coroutine_fn v9fs_write(void *opaque)
> return;
> }
> offset += err;
> - v9fs_init_qiov_from_pdu(&qiov_full, pdu, offset, count, true);
> + v9fs_init_qiov_from_pdu(&qiov_full, pdu, offset, &count, true);
> trace_v9fs_write(pdu->tag, pdu->id, fid, off, count, qiov_full.niov);
>
> fidp = get_fid(pdu, fid);
> diff --git a/hw/9pfs/9p.h b/hw/9pfs/9p.h
> index 8883761b2c..50f7e21da6 100644
> --- a/hw/9pfs/9p.h
> +++ b/hw/9pfs/9p.h
> @@ -365,7 +365,7 @@ struct V9fsTransport {
> ssize_t (*pdu_vunmarshal)(V9fsPDU *pdu, size_t offset, const char
> *fmt, va_list ap);
> void (*init_in_iov_from_pdu)(V9fsPDU *pdu, struct iovec **piov,
> - unsigned int *pniov, size_t size);
> + unsigned int *pniov, size_t *size);
> void (*init_out_iov_from_pdu)(V9fsPDU *pdu, struct iovec **piov,
> unsigned int *pniov, size_t size); void (*push_and_notify)(V9fsPDU
> *pdu);
> diff --git a/hw/9pfs/virtio-9p-device.c b/hw/9pfs/virtio-9p-device.c
> index 775e8ff766..68873c3f5f 100644
> --- a/hw/9pfs/virtio-9p-device.c
> +++ b/hw/9pfs/virtio-9p-device.c
> @@ -145,19 +145,15 @@ static ssize_t virtio_pdu_vunmarshal(V9fsPDU *pdu,
> size_t offset, }
>
> static void virtio_init_in_iov_from_pdu(V9fsPDU *pdu, struct iovec **piov,
> - unsigned int *pniov, size_t size)
> + unsigned int *pniov, size_t *size)
> {
> V9fsState *s = pdu->s;
> V9fsVirtioState *v = container_of(s, V9fsVirtioState, state);
> VirtQueueElement *elem = v->elems[pdu->idx];
> size_t buf_size = iov_size(elem->in_sg, elem->in_num);
>
> - if (buf_size < size) {
> - VirtIODevice *vdev = VIRTIO_DEVICE(v);
> -
> - virtio_error(vdev,
> - "VirtFS reply type %d needs %zu bytes, buffer has
> %zu", - pdu->id + 1, size, buf_size);
> + if (buf_size < *size) {
> + *size = buf_size;
> }
>
> *piov = elem->in_sg;
> diff --git a/hw/9pfs/xen-9p-backend.c b/hw/9pfs/xen-9p-backend.c
> index 3f54a21c76..3994a356d4 100644
> --- a/hw/9pfs/xen-9p-backend.c
> +++ b/hw/9pfs/xen-9p-backend.c
> @@ -187,7 +187,7 @@ static void xen_9pfs_init_out_iov_from_pdu(V9fsPDU *pdu,
> static void xen_9pfs_init_in_iov_from_pdu(V9fsPDU *pdu,
> struct iovec **piov,
> unsigned int *pniov,
> - size_t size)
> + size_t *size)
> {
> Xen9pfsDev *xen_9pfs = container_of(pdu->s, Xen9pfsDev, state);
> Xen9pfsRing *ring = &xen_9pfs->rings[pdu->tag % xen_9pfs->num_rings];
> @@ -197,15 +197,11 @@ static void xen_9pfs_init_in_iov_from_pdu(V9fsPDU
> *pdu, g_free(ring->sg);
>
> ring->sg = g_malloc0(sizeof(*ring->sg) * 2);
> - xen_9pfs_in_sg(ring, ring->sg, &num, pdu->idx, size);
> + xen_9pfs_in_sg(ring, ring->sg, &num, pdu->idx, *size);
>
> buf_size = iov_size(ring->sg, num);
> - if (buf_size < size) {
> - xen_pv_printf(&xen_9pfs->xendev, 0, "Xen 9pfs request type %d"
> - "needs %zu bytes, buffer has %zu\n", pdu->id, size,
> - buf_size);
> - xen_be_set_state(&xen_9pfs->xendev, XenbusStateClosing);
> - xen_9pfs_disconnect(&xen_9pfs->xendev);
> + if (buf_size < *size) {
> + *size = buf_size;
> }
>
> *piov = ring->sg;
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2019-12-19 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 0:42 [PATCH] 9p: init_in_iov_from_pdu can truncate the size Stefano Stabellini
2019-12-19 17:08 ` Christian Schoenebeck [this message]
2019-12-19 22:36 ` Stefano Stabellini
2019-12-20 12:31 ` Christian Schoenebeck
2020-01-06 13:42 ` Greg Kurz
2020-01-06 15:24 ` Christian Schoenebeck
2020-01-06 17:31 ` Greg Kurz
2020-01-06 19:30 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2734053.qHGH40kZ6z@silver \
--to=qemu_oss@crudebyte.com \
--cc=anthony.perard@citrix.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@xilinx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.