qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 7/9] ui: avoid 'local_err' variable shadowing in VNC SASL auth
Date: Fri, 16 Feb 2018 12:54:08 +0100	[thread overview]
Message-ID: <20180216115410.27287-8-kraxel@redhat.com> (raw)
In-Reply-To: <20180216115410.27287-1-kraxel@redhat.com>

From: Daniel P. Berrangé <berrange@redhat.com>

The start_auth_sasl() method declares a 'Error *local_err' variable in
an inner if () {...} scope, which shadows a variable of the same name
declared at the start of the method. This is confusing for reviewers and
may trigger compiler warnings.

Reported-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-id: 20180205114938.15784-3-berrange@redhat.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
 ui/vnc-auth-sasl.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/ui/vnc-auth-sasl.c b/ui/vnc-auth-sasl.c
index fbccca8c8a..8ebd0d3d00 100644
--- a/ui/vnc-auth-sasl.c
+++ b/ui/vnc-auth-sasl.c
@@ -556,7 +556,6 @@ void start_auth_sasl(VncState *vs)
     /* Inform SASL that we've got an external SSF layer from TLS/x509 */
     if (vs->auth == VNC_AUTH_VENCRYPT &&
         vs->subauth == VNC_AUTH_VENCRYPT_X509SASL) {
-        Error *local_err = NULL;
         int keysize;
         sasl_ssf_t ssf;
 
@@ -565,7 +564,6 @@ void start_auth_sasl(VncState *vs)
         if (keysize < 0) {
             trace_vnc_auth_fail(vs, vs->auth, "cannot TLS get cipher size",
                                 error_get_pretty(local_err));
-            error_free(local_err);
             sasl_dispose(&vs->sasl.conn);
             vs->sasl.conn = NULL;
             goto authabort;
-- 
2.9.3

  parent reply	other threads:[~2018-02-16 11:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 11:54 [Qemu-devel] [PULL 0/9] Ui 20180216 patches Gerd Hoffmann
2018-02-16 11:54 ` [Qemu-devel] [PULL 1/9] vnc: remove bogus object_unref on client socket Gerd Hoffmann
2018-02-16 11:54 ` [Qemu-devel] [PULL 2/9] vnc: add qapi/error.h include to stubs Gerd Hoffmann
2018-02-16 11:54 ` [Qemu-devel] [PULL 3/9] vnc: fix segfault in closed connection handling Gerd Hoffmann
2018-02-16 11:54 ` [Qemu-devel] [PULL 4/9] sdl: restore optimized redraw Gerd Hoffmann
2018-04-27 13:08   ` Peter Maydell
2018-02-16 11:54 ` [Qemu-devel] [PULL 5/9] sdl2: fix mouse grab Gerd Hoffmann
2018-02-16 11:54 ` [Qemu-devel] [PULL 6/9] ui: avoid risk of 32-bit int overflow in VNC buffer check Gerd Hoffmann
2018-02-16 11:54 ` Gerd Hoffmann [this message]
2018-02-16 11:54 ` [Qemu-devel] [PULL 8/9] ui: check VNC audio frequency limit at time of reading from client Gerd Hoffmann
2018-02-16 11:54 ` [Qemu-devel] [PULL 9/9] ui: extend VNC trottling tracing to SASL codepaths Gerd Hoffmann
2018-02-16 16:46 ` [Qemu-devel] [PULL 0/9] Ui 20180216 patches Peter Maydell

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=20180216115410.27287-8-kraxel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=berrange@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).