Closed Bug 434808 Opened 13 years ago Closed 13 years ago

"certutil -B" deadlock when importing two or more roots

Categories

(NSS :: Tools, defect, P1)

3.12
x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED
3.12.1

People

(Reporter: KaiE, Assigned: julien.pierre)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

Attachments

(3 files)

r1
1.39 KB, application/octet-stream
Details
r2
1002 bytes, application/octet-stream
Details
58 bytes, text/plain
Details
Using out latest NSPR and NSS sources from trunk, 
I get a deadlock when starting the following command, using the attached three files.

The cert files don't seem to matter.
Nicknames don't seem to matter

I'm operating on an empty cert db, that got created with 
  certutil -d db -N (no password)

Contents of batch file:
 -A -n "r1" -t "CT,C," -i r1
 -A -n "r2" -t "CT,C," -i r2

(gdb) bt
#0  0x00110416 in __kernel_vsyscall ()
#1  0x00b8fb95 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0x003896e3 in PR_WaitCondVar (cvar=0x86f0ed8, timeout=4294967295) at ../../../../pr/src/pthreads/ptsynch.c:405
#3  0x00392290 in PR_Cleanup () at ../../../../pr/src/pthreads/ptthread.c:1035
#4  0x080560c6 in certutil_main (argc=9, argv=0x86f0848, initialize=0) at certutil.c:2895
#5  0x0805604f in certutil_main (argc=6, argv=0xbfe578e4, initialize=1) at certutil.c:2883
#6  0x0805611d in main (argc=Cannot access memory at address 0x80
) at certutil.c:2907
certutil -B -i batch -d db/
Attached file r1
Attached file r2
Attached file batch
Doing some testing, this seems to have been introduced between
  3.12 Beta 1
and
  3.12 Beta 2
Keywords: regression
Regression might have been introduced by bug 415167.
Depends on: 415167
This should be fixed in 3.12.1 by the additional patch checked in, see bug 415167.

Not sure if this can be fixed in 3.12.0, probably not.
Target Milestone: --- → 3.12.1
Assignee: nobody → julien.pierre.boogz
Priority: -- → P1
I'm marking this fixed. It was fixed with a checked in done in bug 434808
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.