Closed
Bug 1925512
Opened 1 year ago
Closed 1 year ago
Thread safety of `lockStatus` and `locksEverDisabled`
Categories
(NSS :: Libraries, defect, P3)
NSS
Libraries
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mdauer, Assigned: mdauer)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
sslLockStatus and locksEverDisabled are global variables and may cause thread safety issues if multiple threads for example call SSL_OptionSet with SSL_NO_LOCKS. They don't seem to be actually used anywhere, so I guess it would make sense to simply remove them?
|
Assignee | |
Updated•1 year ago
|
Severity: -- → S4
Priority: -- → P3
|
|
Assignee | |
Updated•1 year ago
|
Assignee: nobody → mdauer
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 1•1 year ago
|
||
These are not thread-safe and aren't used anywhere, so we can just remove them.
|
|
Assignee | |
Comment 2•1 year ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
|
||
Updated•11 months ago
|
Blocks: nss-fuzzing-bugs
You need to log in
before you can comment on or make changes to this bug.
Description
•