Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMatthew Harmsen
2011-02-09 00:25:44 UTC
+++ This bug was initially created as a clone of Bug #676083 +++
This was actually reported by Bob Relyea verbally, and I have confirmed the bug:
in JSS, there are places where PK11_GetInternalSlot() is called but never freed.
The most obvious ones are the ones that are called and used directly for comparison and not assigned to any variable (hence unfreeable).
The right way to do this is something like this:
PK11SlotInfo *aSlot = NULL;
...
...
aSlot = PK11_GetInternalSlot();
...
...
finish:
if (aSlot != NULL) {
PK11_FreeSlot(aSlot);
}
What you don't want to do is something like this:
if (slot != PK11_GetInternalSlot()) ...
if not fixed, other than memory leak, there are potential consequences such as
NSS may not be able to release the slot due to some internal counters.
Bob might be able to fill in on the detail.
--- Additional comment from rrelyea on 2011-02-08 14:31:58 EST ---
Most of the usages can be replaced by NSS functions that give better answers:
PK11_IsInternalKeySlot(slot) returns true if the slot is the default internal key slot.
PK11_IsInternal(slot) return true if the slot is any type of internal slot. Several of your checks should probably use this test as there can be more than one database slot these days.
The code I noticed this in is CryptoManager.c
bob
Can you please add steps to reproduce this bug. Thanks!
Comment 5Chandrasekar Kannan
2011-04-20 23:31:44 UTC
I don't think its going to be easy for QE to verify this. I'm going to suggest a peer code review by another dev as a verification method for this.
Comment 6Chandrasekar Kannan
2011-04-29 01:05:10 UTC
marking it VERIFIED with VERIFIED field set to SanityOnly. Layered components on top of this that are pki-ca and IPA are functioning normally through our regression tests.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0621.html