From 120408c1516d39bccbdfc8ed8dfdf620d9908179 Mon Sep 17 00:00:00 2001 From: Greg Hudson Date: Wed, 1 Aug 2012 14:43:43 -0400 Subject: Explain memory allocation policy in oid_ops.c --- src/lib/gssapi/generic/oid_ops.c | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'src/lib') 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 #include +/* + * 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) { -- cgit