From: Steve Dickson <SteveD@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] gssd: avoid double-free upon write failure
Date: Thu, 05 Jan 2012 16:43:06 -0500 [thread overview]
Message-ID: <4F06196A.60900@RedHat.com> (raw)
In-Reply-To: <87lipqumid.fsf@rho.meyering.net>
On 01/02/2012 10:55 AM, Jim Meyering wrote:
>
> * utils/gssd/context_lucid.c (prepare_krb5_rfc1964_buffer): Free just-
> calloc'd enc_key.data from one place, unconditionally, after calling
> write_lucid_keyblock, rather than from three places. Before, upon
> failed write, we would free it, then goto out_err, where we would
> free it again, if it happened to be non-NULL.
> Coverity spotted the possible double free.
Committed....
steved.
> ---
> utils/gssd/context_lucid.c | 9 ++++-----
> 1 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/utils/gssd/context_lucid.c b/utils/gssd/context_lucid.c
> index 3e695ab..64146d7 100644
> --- a/utils/gssd/context_lucid.c
> +++ b/utils/gssd/context_lucid.c
> @@ -80,6 +80,7 @@ prepare_krb5_rfc1964_buffer(gss_krb5_lucid_context_v1_t *lctx,
> uint32_t i;
> char *skd, *dkd;
> gss_buffer_desc fakeoid;
> + int err;
>
> /*
> * The new Kerberos interface to get the gss context
> @@ -138,11 +139,10 @@ prepare_krb5_rfc1964_buffer(gss_krb5_lucid_context_v1_t *lctx,
> dkd = (char *) enc_key.data;
> for (i = 0; i < enc_key.length; i++)
> dkd[i] = skd[i] ^ 0xf0;
> - if (write_lucid_keyblock(&p, end, &enc_key)) {
> - free(enc_key.data);
> - goto out_err;
> - }
> + err = write_lucid_keyblock(&p, end, &enc_key);
> free(enc_key.data);
> + if (err)
> + goto out_err;
>
> if (write_lucid_keyblock(&p, end, &lctx->rfc1964_kd.ctx_key))
> goto out_err;
> @@ -153,7 +153,6 @@ out_err:
> printerr(0, "ERROR: failed serializing krb5 context for kernel\n");
> if (buf->value) free(buf->value);
> buf->length = 0;
> - if (enc_key.data) free(enc_key.data);
> return -1;
> }
>
> --
> 1.7.8.1.391.g2c2ad
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-01-05 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 15:55 [PATCH] gssd: avoid double-free upon write failure Jim Meyering
2012-01-05 21:43 ` Steve Dickson [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=4F06196A.60900@RedHat.com \
--to=steved@redhat.com \
--cc=jim@meyering.net \
--cc=linux-nfs@vger.kernel.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).