Linux virtualization list
 help / color / mirror / Atom feed
From: Stefano Garzarella <sgarzare@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [RFC PATCH 10/10] vhost/vdpa: return configuration bytes read and written to user space
Date: Fri, 5 Mar 2021 09:37:12 +0100	[thread overview]
Message-ID: <20210305083712.atfrlpq6bkjrf6pd@steredhat> (raw)
In-Reply-To: <5cf852b1-1279-20e9-516d-30f876e0162d@redhat.com>

On Thu, Mar 04, 2021 at 04:31:22PM +0800, Jason Wang wrote:
>
>On 2021/3/2 10:06 下午, Stefano Garzarella wrote:
>>On Tue, Mar 02, 2021 at 12:05:35PM +0800, Jason Wang wrote:
>>>
>>>On 2021/2/16 5:44 下午, Stefano Garzarella wrote:
>>>>vdpa_get_config() and vdpa_set_config() now return the amount
>>>>of bytes read and written, so let's return them to the user space.
>>>>
>>>>We also modify vhost_vdpa_config_validate() to return 0 (bytes read
>>>>or written) instead of an error, when the buffer length is 0.
>>>>
>>>>Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
>>>>---
>>>> drivers/vhost/vdpa.c | 26 +++++++++++++++-----------
>>>> 1 file changed, 15 insertions(+), 11 deletions(-)
>>>>
>>>>diff --git a/drivers/vhost/vdpa.c b/drivers/vhost/vdpa.c
>>>>index 21eea2be5afa..b754c53171a7 100644
>>>>--- a/drivers/vhost/vdpa.c
>>>>+++ b/drivers/vhost/vdpa.c
>>>>@@ -191,9 +191,6 @@ static ssize_t 
>>>>vhost_vdpa_config_validate(struct vhost_vdpa *v,
>>>>     struct vdpa_device *vdpa = v->vdpa;
>>>>     u32 size = vdpa->config->get_config_size(vdpa);
>>>>-    if (c->len == 0)
>>>>-        return -EINVAL;
>>>>-
>>>>     return min(c->len, size);
>>>> }
>>>>@@ -204,6 +201,7 @@ static long vhost_vdpa_get_config(struct 
>>>>vhost_vdpa *v,
>>>>     struct vhost_vdpa_config config;
>>>>     unsigned long size = offsetof(struct vhost_vdpa_config, buf);
>>>>     ssize_t config_size;
>>>>+    long ret;
>>>>     u8 *buf;
>>>>     if (copy_from_user(&config, c, size))
>>>>@@ -217,15 +215,18 @@ static long vhost_vdpa_get_config(struct 
>>>>vhost_vdpa *v,
>>>>     if (!buf)
>>>>         return -ENOMEM;
>>>>-    vdpa_get_config(vdpa, config.off, buf, config_size);
>>>>-
>>>>-    if (copy_to_user(c->buf, buf, config_size)) {
>>>>-        kvfree(buf);
>>>>-        return -EFAULT;
>>>>+    ret = vdpa_get_config(vdpa, config.off, buf, config_size);
>>>>+    if (ret < 0) {
>>>>+        ret = -EFAULT;
>>>>+        goto out;
>>>>     }
>>>>+    if (copy_to_user(c->buf, buf, config_size))
>>>>+        ret = -EFAULT;
>>>>+
>>>>+out:
>>>>     kvfree(buf);
>>>>-    return 0;
>>>>+    return ret;
>>>> }
>>>> static long vhost_vdpa_set_config(struct vhost_vdpa *v,
>>>>@@ -235,6 +236,7 @@ static long vhost_vdpa_set_config(struct 
>>>>vhost_vdpa *v,
>>>>     struct vhost_vdpa_config config;
>>>>     unsigned long size = offsetof(struct vhost_vdpa_config, buf);
>>>>     ssize_t config_size;
>>>>+    long ret;
>>>>     u8 *buf;
>>>>     if (copy_from_user(&config, c, size))
>>>>@@ -248,10 +250,12 @@ static long vhost_vdpa_set_config(struct 
>>>>vhost_vdpa *v,
>>>>     if (IS_ERR(buf))
>>>>         return PTR_ERR(buf);
>>>>-    vdpa_set_config(vdpa, config.off, buf, config_size);
>>>>+    ret = vdpa_set_config(vdpa, config.off, buf, config_size);
>>>>+    if (ret < 0)
>>>>+        ret = -EFAULT;
>>>>     kvfree(buf);
>>>>-    return 0;
>>>>+    return ret;
>>>> }
>>>
>>>
>>>So I wonder whether it's worth to return the number of bytes since 
>>>we can't propogate the result to driver or driver doesn't care 
>>>about that.
>>
>>Okay, but IIUC user space application that issue 
>>VHOST_VDPA_GET_CONFIG ioctl can use the return value.
>
>
>Yes, but it looks to it's too late to change since it's a userspace 
>noticble behaviour.

Yeah, this is a good point.
I looked at QEMU and we only check if the value is not negative, so it 
should work, but for other applications it could be a real change.

Do we leave it as is?

>
>
>>
>>Should we change also 'struct virtio_config_ops' to propagate this 
>>value also to virtio drivers?
>
>
>I think not, the reason is the driver doesn't expect the get()/set() 
>can fail...

Got it.

Thanks,
Stefano

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2021-03-05  8:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16  9:44 [RFC PATCH 00/10] vdpa: get/set_config() rework Stefano Garzarella
2021-02-16  9:44 ` [RFC PATCH 01/10] vdpa: add get_config_size callback in vdpa_config_ops Stefano Garzarella
2021-03-02  4:14   ` Jason Wang
2021-03-02 14:15     ` Stefano Garzarella
2021-03-04  8:34       ` Jason Wang
2021-03-05  8:38         ` Stefano Garzarella
2021-02-16  9:44 ` [RFC PATCH 02/10] vdpa: check vdpa_get_config() parameters and return bytes read Stefano Garzarella
2021-02-16  9:44 ` [RFC PATCH 03/10] vdpa: add vdpa_set_config() helper Stefano Garzarella
2021-02-16  9:44 ` [RFC PATCH 04/10] vdpa: remove param checks in the get/set_config callbacks Stefano Garzarella
2021-02-16  9:44 ` [RFC PATCH 05/10] vdpa: remove WARN_ON() " Stefano Garzarella
2021-02-16  9:44 ` [RFC PATCH 06/10] virtio_vdpa: use vdpa_set_config() Stefano Garzarella
2021-02-16  9:44 ` [RFC PATCH 07/10] vhost/vdpa: " Stefano Garzarella
2021-02-16  9:44 ` [RFC PATCH 08/10] vhost/vdpa: allow user space to pass buffers bigger than config space Stefano Garzarella
2021-02-16  9:44 ` [RFC PATCH 09/10] vhost/vdpa: use get_config_size callback in vhost_vdpa_config_validate() Stefano Garzarella
2021-02-16  9:44 ` [RFC PATCH 10/10] vhost/vdpa: return configuration bytes read and written to user space Stefano Garzarella
2021-03-02  4:05   ` Jason Wang
2021-03-02 14:06     ` Stefano Garzarella
2021-03-04  8:31       ` Jason Wang
2021-03-05  8:37         ` Stefano Garzarella [this message]
2021-03-08  3:59           ` Jason Wang
2021-03-01  8:17 ` [RFC PATCH 00/10] vdpa: get/set_config() rework Stefano Garzarella

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=20210305083712.atfrlpq6bkjrf6pd@steredhat \
    --to=sgarzare@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox