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.
Elio, no upstream bug has been linked to this yet.
bob
Comment 7Elio Maldonado Batiz
2012-03-14 16:10:40 UTC
(In reply to comment #5)
See External tracker. Fixed upstream and this bug gets fixed by updating to 3.13.3.
Comment 10Elio Maldonado Batiz
2012-04-26 18:28:55 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
No documentation needed
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2012-0973.html
Description of problem: The increment of softokenLoadCount is not in par with its decrement. Version-Release number of selected component (if applicable): nss-3.12.10-17.1.el6 How reproducible: 100 % Steps to Reproduce: 1. run the attached test-case Actual results: (gdb) break pk11load.c:600 Breakpoint 1 at 0x3d59c4992c: file pk11load.c, line 600. (gdb) run Breakpoint 1, SECMOD_UnloadModule (mod=0x67dae0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { (gdb) display softokenLoadCount (gdb) continue Breakpoint 1, SECMOD_UnloadModule (mod=0x612dc0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 3 (gdb) Breakpoint 1, SECMOD_UnloadModule (mod=0x67b9e0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 2 (gdb) print mod->moduleDBFunc $1 = (void *) 0x330a40ddc0 (gdb) info symbol mod->moduleDBFunc NSC_ModuleDBFunc in section .text of /usr/lib64/libsoftokn3.so (gdb) continue Breakpoint 1, SECMOD_UnloadModule (mod=0x612080) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 1 (gdb) Breakpoint 1, SECMOD_UnloadModule (mod=0x610ba0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 0 (gdb) test_instance() succeeded 0/16 Breakpoint 1, SECMOD_UnloadModule (mod=0x6732c0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 3 (gdb) Breakpoint 1, SECMOD_UnloadModule (mod=0x67b9e0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 2 (gdb) Breakpoint 1, SECMOD_UnloadModule (mod=0x612dc0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 1 (gdb) Breakpoint 1, SECMOD_UnloadModule (mod=0x612080) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 0 (gdb) Breakpoint 1, SECMOD_UnloadModule (mod=0x610ba0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = -1 (gdb) test_instance() succeeded 1/16 Breakpoint 1, SECMOD_UnloadModule (mod=0x6716b0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 2 (gdb) Breakpoint 1, SECMOD_UnloadModule (mod=0x612dc0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 1 (gdb) Breakpoint 1, SECMOD_UnloadModule (mod=0x63c580) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 0 (gdb) Breakpoint 1, SECMOD_UnloadModule (mod=0x612080) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = -1 (gdb) Breakpoint 1, SECMOD_UnloadModule (mod=0x610ba0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = -2 (gdb) test_instance() succeeded 2/16 Breakpoint 1, SECMOD_UnloadModule (mod=0x6e8de0) at pk11load.c:600 600 if (0 == PR_ATOMIC_DECREMENT(&softokenLoadCount)) { 1: softokenLoadCount = 1 (gdb) Program received signal SIGSEGV, Segmentation fault. 0x000000330a40ddc0 in ?? () (gdb) up #1 0x0000003d59c589be in SECMOD_FreeModuleSpecList (module=0x610ba0, moduleSpecList=0x60d110) at pk11pars.c:1077 1077 retString = (*func)(SECMOD_MODULE_DB_FUNCTION_RELEASE, (gdb) print func $2 = (SECMODModuleDBFunc) 0x330a40ddc0 (gdb) info symbol func No symbol matches func.