Closed
Bug 1705119
Opened 3 years ago
Closed 3 years ago
Deadlock when using gcm and non-thread safe tokens.
Categories
(NSS :: Libraries, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rrelyea, Assigned: rrelyea)
Details
Attachments
(1 file)
The GCM support introduced a deadlock when using GCM message interface that only manifests in non-threadsafe tokens.
Assignee | ||
Comment 1•3 years ago
|
||
I'll attach a patch sortly that will 1) allow testing softoken as a non-threadsafe token to our tests (in debug mode with appropriate env variable). and 2) fix the gcm deadlock by reducing the context monitor (which maps to the slot monitor) to only trigger around the actual PKCS #11 calls (since it's purpose in that case is only to protect the token from multiple entries into the token from different threads).
Assignee: nobody → rrelyea
Assignee | ||
Comment 2•3 years ago
|
||
- Add code to treat softokn as a non-threadsafe module.
- Add a cycle to test ssl against non-threadafe modules.
- Fix deadlock by restricting the ContextMonitor to only be active around PKCS #11 function calls.
Assignee | ||
Updated•3 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•3 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•