From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, kwolf@redhat.com, mreitz@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH 3/5] nbd/server: add helper nbd_opt_invalid
Date: Wed, 22 Nov 2017 15:59:44 -0600 [thread overview]
Message-ID: <2ab4c650-e5c3-8751-aa20-af328cd9308d@redhat.com> (raw)
In-Reply-To: <20171122101958.17065-4-vsementsov@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On 11/22/2017 04:19 AM, Vladimir Sementsov-Ogievskiy wrote:
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> nbd/server.c | 74 +++++++++++++++++++++++++++++++++++++-----------------------
> 1 file changed, 46 insertions(+), 28 deletions(-)
>
> +/* nbd_opt_invalid
> + * Drop reminded option data and reply with NBD_REP_ERR_INVALID
s/reminded/the remainder of/
In fact, if we generalize this just a bit more, and let the caller
choose whether to use NBD_REP_ERR_INVALID or NBD_REP_ERR_TLS_REQD or
NBD_REP_ERR_UNSUP, then we can merge this functionality directly into
nbd_opt_drop() instead of adding another function. I guess I'll have to
merge that into the counter-proposal I have in mind (but at this point,
the counter-proposal won't be posted any sooner than 2.11-rc3, in part
because I'm almost on my Thanksgiving vacation).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-11-22 21:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 10:19 [Qemu-devel] [PATCH 0/5] NBD server refactoring before BLOCK_STATUS Vladimir Sementsov-Ogievskiy
2017-11-22 10:19 ` [Qemu-devel] [PATCH 1/5] nbd/server: refactor negotiation functions parameters Vladimir Sementsov-Ogievskiy
2017-11-22 16:39 ` Eric Blake
2017-11-22 10:19 ` [Qemu-devel] [PATCH 2/5] nbd/server: add nbd_opt_{read, drop} to track client->optlen Vladimir Sementsov-Ogievskiy
2017-11-22 17:08 ` Eric Blake
2017-11-22 19:22 ` Eric Blake
2017-11-22 20:03 ` Eric Blake
2017-12-21 1:38 ` Eric Blake
2017-11-22 10:19 ` [Qemu-devel] [PATCH 3/5] nbd/server: add helper nbd_opt_invalid Vladimir Sementsov-Ogievskiy
2017-11-22 21:59 ` Eric Blake [this message]
2017-11-22 23:00 ` Eric Blake
2017-11-22 10:19 ` [Qemu-devel] [PATCH 4/5] nbd: rename nbd_option and nbd_opt_reply Vladimir Sementsov-Ogievskiy
2017-11-22 21:56 ` Eric Blake
2018-01-10 18:11 ` Eric Blake
2017-11-22 10:19 ` [Qemu-devel] [PATCH 5/5] nbd/server: structurize option reply sending Vladimir Sementsov-Ogievskiy
2017-11-22 22:02 ` Eric Blake
2018-01-10 18:14 ` Eric Blake
2017-11-22 11:07 ` [Qemu-devel] [PATCH 0/5] NBD server refactoring before BLOCK_STATUS no-reply
2017-11-22 11:54 ` [Qemu-devel] unrelated " Vladimir Sementsov-Ogievskiy
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=2ab4c650-e5c3-8751-aa20-af328cd9308d@redhat.com \
--to=eblake@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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 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).