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

RESOLVED FIXED in 3.12.1

Status

NSS
Tools
P1
normal
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: kaie, Assigned: Julien Pierre)

Tracking

(Blocks: 1 bug, {regression})

3.12
3.12.1
x86
Linux
regression
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

r1
1.39 KB, application/octet-stream
Details
r2
1002 bytes, application/octet-stream
Details
58 bytes, text/plain
Details
(Reporter)

Description

9 years ago
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
(Reporter)

Comment 1

9 years ago
certutil -B -i batch -d db/
(Reporter)

Comment 2

9 years ago
Created attachment 321798 [details]
r1
(Reporter)

Comment 3

9 years ago
Created attachment 321799 [details]
r2
(Reporter)

Comment 4

9 years ago
Created attachment 321800 [details]
batch
(Reporter)

Comment 5

9 years ago
Doing some testing, this seems to have been introduced between
  3.12 Beta 1
and
  3.12 Beta 2
(Reporter)

Updated

9 years ago
Keywords: regression
(Reporter)

Comment 6

9 years ago
Regression might have been introduced by bug 415167.
(Reporter)

Updated

9 years ago
Depends on: 415167
(Reporter)

Comment 7

9 years ago
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
Blocks: 436376
Assignee: nobody → julien.pierre.boogz
Priority: -- → P1
(Reporter)

Comment 8

9 years ago
I'm marking this fixed. It was fixed with a checked in done in bug 434808
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.