From: Greg Hudson <ghudson@mit.edu>
Date: Wed, 1 Aug 2012 18:43:43 +0000 (-0400)
Subject: Explain memory allocation policy in oid_ops.c
X-Git-Tag: krb5-1.11-alpha1~365
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=120408c1516d39bccbdfc8ed8dfdf620d9908179;p=thirdparty%2Fkrb5.git

Explain memory allocation policy in oid_ops.c
---

diff --git a/src/lib/gssapi/generic/oid_ops.c b/src/lib/gssapi/generic/oid_ops.c
index 1159efeb72..ff5096d604 100644
--- a/src/lib/gssapi/generic/oid_ops.c
+++ b/src/lib/gssapi/generic/oid_ops.c
@@ -58,6 +58,13 @@
 #include <errno.h>
 #include <ctype.h>
 
+/*
+ * The functions for allocating and releasing individual OIDs use malloc and
+ * free instead of the gssalloc wrappers, because the mechglue currently mixes
+ * generic_gss_copy_oid() with hand-freeing of OIDs.  We do not need to free
+ * free OIDs allocated by mechanisms, so this should not be a problem.
+ */
+
 OM_uint32
 generic_gss_release_oid(OM_uint32 *minor_status, gss_OID *oid)
 {