From: Wouter Verhelst <w@uter.be>
To: Alex Bligh <alex@alex.org.uk>
Cc: "nbd-general@lists.sourceforge.net"
<nbd-general@lists.sourceforge.net>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Nbd] [PATCH] Docs: proto.md: Clarify NUL in export name
Date: Fri, 1 Apr 2016 10:37:19 +0200 [thread overview]
Message-ID: <20160401083719.GE25514@grep.be> (raw)
In-Reply-To: <1459466208-56393-1-git-send-email-alex@alex.org.uk>
Thanks, applied.
On Fri, Apr 01, 2016 at 12:16:48AM +0100, Alex Bligh wrote:
> Clarify that
>
> * The name is not NUL terminated (not just that the length
> 'does not include NUL termination' which might be taken to mean
> there is NUL termination but the length doesn't include it.
>
> * The name cannot itself include embedded NUL characters (despite
> it not being NUL terminated).
>
> Signed-off-by: Alex Bligh <alex@alex.org.uk>
> ---
> doc/proto.md | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/doc/proto.md b/doc/proto.md
> index c1e05c5..7729051 100644
> --- a/doc/proto.md
> +++ b/doc/proto.md
> @@ -292,7 +292,8 @@ of the newstyle negotiation.
> haggling, and proceed to the transmission phase. Data: name of the
> export, free-form UTF-8 text (subject to limitations by server
> implementation). The length of the name is determined from the
> - option header, and does NOT include a NUL terminator. If the
> + option header. The name is not NUL terminated, and may not
> + contain embedded NUL characters. If the
> chosen export does not exist or requirements for the chosen export
> are not met (e.g., the client did not negotiate TLS for an export
> where the server requires it), the server should close the
> --
> 1.9.1
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
> _______________________________________________
> Nbd-general mailing list
> Nbd-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nbd-general
>
--
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
people in the world who think they really understand all of its rules,
and pretty much all of them are just lying to themselves too.
-- #debian-devel, OFTC, 2016-02-12
prev parent reply other threads:[~2016-04-01 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 23:16 [Qemu-devel] [PATCH] Docs: proto.md: Clarify NUL in export name Alex Bligh
2016-04-01 8:37 ` Wouter Verhelst [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=20160401083719.GE25514@grep.be \
--to=w@uter.be \
--cc=alex@alex.org.uk \
--cc=nbd-general@lists.sourceforge.net \
--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).