Closed Bug 205717 Opened 21 years ago Closed 2 years ago

PK11_InitSlot should lock around the C_GetSlotInfo call

Categories

(NSS :: Libraries, defect, P3)

3.78
defect

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.
QA Contact: bishakhabanerjee → jason.m.reid
QA Contact: jason.m.reid → libraries
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.

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.

Assignee: wtc → nobody

John, do you think this might still be relevant?

Flags: needinfo?(jschanck)

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: nobody → jschanck
Blocks: 1763237
Priority: -- → P3
Whiteboard: [nss-fx]
Version: 3.8 → 3.78
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: