From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] sockets: avoid formatting buffer that may not be NULL terminated
Date: Mon, 26 Jun 2017 12:19:40 +0200 [thread overview]
Message-ID: <c4381bd8-a417-0c3b-f3c2-1292ca9f6dfc@redhat.com> (raw)
In-Reply-To: <20170626101159.19676-1-berrange@redhat.com>
On 26.06.2017 12:11, Daniel P. Berrange wrote:
> The 'sun_path' field in the sockaddr_un struct is not required
> to be NULL termianted, so when reporting an error, we must use
s/NULL/NUL/
NULL is a pointer, NUL is the '\0' character.
> the separate 'path' variable which is guaranteed terminated.
>
> Fixes a bug spotted by coverity that was introduced in
>
> commit ad9579aaa16d5b385922d49edac2c96c79bcfb62
> Author: Daniel P. Berrange <berrange@redhat.com>
> Date: Thu May 25 16:53:00 2017 +0100
>
> sockets: improve error reporting if UNIX socket path is too long
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> util/qemu-sockets.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/util/qemu-sockets.c b/util/qemu-sockets.c
> index 51bf279..37d386f 100644
> --- a/util/qemu-sockets.c
> +++ b/util/qemu-sockets.c
> @@ -930,7 +930,7 @@ static int unix_listen_saddr(UnixSocketAddress *saddr,
> strncpy(un.sun_path, path, sizeof(un.sun_path));
>
> if (bind(sock, (struct sockaddr*) &un, sizeof(un)) < 0) {
> - error_setg_errno(errp, errno, "Failed to bind socket to %s", un.sun_path);
> + error_setg_errno(errp, errno, "Failed to bind socket to %s", path);
> goto err;
> }
> if (listen(sock, 1) < 0) {
Apart from the nit in the comment, the patch looks right to me:
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2017-06-26 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 10:11 [Qemu-devel] [PATCH] sockets: avoid formatting buffer that may not be NULL terminated Daniel P. Berrange
2017-06-26 10:19 ` Thomas Huth [this message]
2017-07-05 13:41 ` Stefan Hajnoczi
2017-07-05 13:50 ` Thomas Huth
2017-07-05 15:51 ` Markus Armbruster
2017-07-05 13:41 ` Stefan Hajnoczi
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=c4381bd8-a417-0c3b-f3c2-1292ca9f6dfc@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).