Closed
Bug 205717
Opened 22 years ago
Closed 3 years ago
PK11_InitSlot should lock around the C_GetSlotInfo call
Categories
(NSS :: Libraries, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wtc, Assigned: jschanck)
References
(Blocks 1 open bug)
Details
(Whiteboard: [nss-fx])
Crash Data
Attachments
(1 file)
PK11_InitSlot is not locking around the C_GetSlotInfo
call. This is fine right now because we only initialize
NSS on one thread at startup (NSS only allows one instance
of NSS_Initialize at a time). But it might be a good
idea to lock around the C_GetSlotInfo call anyway.
|
||
Updated•20 years ago
|
QA Contact: bishakhabanerjee → jason.m.reid
|
|
||
Updated•19 years ago
|
QA Contact: jason.m.reid → libraries
|
|
||
Comment 1•18 years ago
|
||
It seems this should be higher priority now that modules can dynamically add slots in PKCS#11 v2.20 . We have SECMOD_UpdateSlotList which may call PK11_InitSlot after NSS initialization, from multiple threads.
|
||
Comment 2•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.
Assignee: wtc → nobody
|
Assignee | |
Comment 4•3 years ago
|
||
Yeah, this doesn't seem safe. And we have crash reports on that line. I'll switch this to a call to PK11_GetSlotInfo.
Crash Signature: [@ beid_ff_pkcs11_32.dll | PK11_InitSlot]
Flags: needinfo?(jschanck)
|
|
Assignee | |
Updated•3 years ago
|
|
|
Assignee | |
Comment 5•3 years ago
|
||
|
|
Assignee | |
Comment 6•3 years ago
|
||
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•