qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@linux.vnet.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] virtio-ccw: assure be accesses for set-revision
Date: Wed, 11 Mar 2015 13:39:33 +0100	[thread overview]
Message-ID: <20150311133933.2288ad79@oc7435384737.ibm.com> (raw)
In-Reply-To: <1426067871-17693-3-git-send-email-cornelia.huck@de.ibm.com>

On Wed, 11 Mar 2015 10:57:51 +0100
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:

> All fields in structures transmitted by ccws are big endian; assure
> we handle them as such for the set-revision ccw as well.
> 
> Should be merged into "s390x/virtio-ccw: add virtio set-revision call".
> 
> CC: Thomas Huth <thuth@linux.vnet.ibm.com>
> Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> ---
>  hw/s390x/virtio-ccw.c | 15 +++++++++++++--
>  1 file changed, 13 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/s390x/virtio-ccw.c b/hw/s390x/virtio-ccw.c
> index 60f8a14..a64f116 100644
> --- a/hw/s390x/virtio-ccw.c
> +++ b/hw/s390x/virtio-ccw.c
> @@ -687,7 +687,7 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
>          break;
>      case CCW_CMD_SET_VIRTIO_REV:
>          len = sizeof(revinfo);
> -        if (ccw.count < len || (check_len && ccw.count > len)) {
> +        if (ccw.count < sizeof(revinfo)) {
>              ret = -EINVAL;
>              break;
>          }
> @@ -695,7 +695,18 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
>              ret = -EFAULT;
>              break;
>          }
> -        cpu_physical_memory_read(ccw.cda, &revinfo, len);
> +        revinfo.revision = lduw_be_phys(&address_space_memory, ccw.cda);
> +        revinfo.length = lduw_be_phys(&address_space_memory,
> +                                   ccw.cda + sizeof(revinfo.revision));
> +        if (ccw.count < len + revinfo.length ||
> +            (check_len && ccw.count > len + revinfo.length)) {
> +            ret = -EINVAL;
> +            break;
> +        }
> +        /*
> +         * Once we start to support revisions with additional data, we'll
> +         * need to fetch it here. Nothing to do for now, though.
> +         */
>          if (dev->revision >= 0 ||
>              revinfo.revision > virtio_ccw_rev_max(dev)) {
>              ret = -ENOSYS;

Looks fine to me.

Reviewed-by: Thomas Huth <thuth@linux.vnet.ibm.com>

      reply	other threads:[~2015-03-11 12:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 13:32 [Qemu-devel] [PATCH] virtio: avoid leading underscores for helpers Cornelia Huck
2015-03-10 14:12 ` Michael S. Tsirkin
2015-03-10 14:22   ` Cornelia Huck
2015-03-10 14:27     ` Michael S. Tsirkin
2015-03-10 16:03       ` Cornelia Huck
2015-03-10 16:34         ` Michael S. Tsirkin
2015-03-10 17:05           ` Cornelia Huck
2015-03-10 17:22             ` [Qemu-devel] [PATCH] virtio: legacy features callback Cornelia Huck
2015-03-11  9:57             ` [Qemu-devel] [PATCH 0/2] virtio-ccw: be accesses Cornelia Huck
2015-03-11  9:57             ` [Qemu-devel] [PATCH 1/2] virtio-ccw: assure BE accesses Cornelia Huck
2015-03-13  9:44               ` Cornelia Huck
2015-03-11  9:57             ` [Qemu-devel] [PATCH 2/2] virtio-ccw: assure be accesses for set-revision Cornelia Huck
2015-03-11 12:39               ` Thomas Huth [this message]

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=20150311133933.2288ad79@oc7435384737.ibm.com \
    --to=thuth@linux.vnet.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).