priority: Use gnutls_free consistently

The whole point of gnutls_calloc() is to allow an alternative to
malloc() where that alternative takes over all aspects of heap
management; as such, it is never safe to pair bare free() with memory
managed by gnutls.  Not to mention that it looks bad to mix calls to
gnutls_free() and free() to the same variable within the same
function.

Signed-off-by: Eric Blake <eblake@redhat.com>

diff --git a/lib/priority.c b/lib/priority.c
index 8ea86d719c41fe4bfd767b9348e933466a6c9aaf..8caf189bc20e306f18b1dda753ba95baa3eec41d 100644 (file)
--- a/lib/priority.c
+++ b/lib/priority.c
@@ -3299,7 +3299,7 @@ gnutls_priority_init(gnutls_priority_t * priority_cache,
        ret = GNUTLS_E_INVALID_REQUEST;
 
  error_cleanup:
-       free(darg);
+       gnutls_free(darg);
        gnutls_priority_deinit(*priority_cache);
        *priority_cache = NULL;