All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
	"open list:Network Block Dev..." <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] nbd/client: Relax handling of large NBD_CMD_BLOCK_STATUS reply
Date: Tue, 29 May 2018 18:34:59 +0300	[thread overview]
Message-ID: <dd9b008a-0e2e-9a4f-5387-e66aecf6feb3@virtuozzo.com> (raw)
In-Reply-To: <20180503222626.1303410-1-eblake@redhat.com>

04.05.2018 01:26, Eric Blake wrote:
> The NBD spec is proposing a relaxation of NBD_CMD_BLOCK_STATUS
> where a server may have the final extent per context give a
> length beyond the original request, if it can easily prove that
> subsequent bytes have the same status, on the grounds that a
> client can take advantage of this information for fewer block
> status requests.  Since qemu 2.12 as a client always sends
> NBD_CMD_FLAG_REQ_ONE, and rejects a server that sends extra
> length, the upstream NBD spec will probably limit this behavior
> to clients that don't request REQ_ONE semantics; but it doesn't
> hurt to relax qemu to always be permissive of this server
> behavior, even if it continues to use REQ_ONE.

Hi!

Patch is applied, are you going to make a patch for NBD spec?

>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>   block/nbd-client.c | 10 +++++++---
>   1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/block/nbd-client.c b/block/nbd-client.c
> index e7caf49fbb4..25d34631fe7 100644
> --- a/block/nbd-client.c
> +++ b/block/nbd-client.c
> @@ -259,14 +259,18 @@ static int nbd_parse_blockstatus_payload(NBDClientSession *client,
>
>       if (extent->length == 0 ||
>           (client->info.min_block && !QEMU_IS_ALIGNED(extent->length,
> -                                                    client->info.min_block)) ||
> -        extent->length > orig_length)
> -    {
> +                                                    client->info.min_block))) {
>           error_setg(errp, "Protocol error: server sent status chunk with "
>                      "invalid length");
>           return -EINVAL;
>       }
>
> +    /* The server is allowed to send us extra information on the final
> +     * extent; just clamp it to the length we requested. */
> +    if (extent->length > orig_length) {
> +        extent->length == orig_length;
> +    }
> +
>       return 0;
>   }
>


-- 
Best regards,
Vladimir

  parent reply	other threads:[~2018-05-29 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 22:26 [Qemu-devel] [PATCH] nbd/client: Relax handling of large NBD_CMD_BLOCK_STATUS reply Eric Blake
2018-05-03 22:30 ` no-reply
2018-05-03 22:35   ` Eric Blake
2018-05-03 23:22 ` no-reply
2018-05-04 10:40 ` Vladimir Sementsov-Ogievskiy
2018-05-04 13:17   ` Eric Blake
2018-05-29 15:34 ` Vladimir Sementsov-Ogievskiy [this message]
2018-05-30  0:52   ` Eric Blake

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=dd9b008a-0e2e-9a4f-5387-e66aecf6feb3@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 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.