[SERVER-51183] Coverity analysis defect 115026: Data race condition Created: 28/Sep/20  Updated: 27/Oct/23  Resolved: 10/May/23

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Coverity Collector User Assignee: Backlog - Service Architecture
Resolution: Works as Designed Votes: 0
Labels: coverity
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Service Arch
Operating System: ALL
Participants:

 Description   

Data race condition

The value of the shared data will be determined by the interleaving of thread execution. Thread shared data is accessed without holding an appropriate lock, possibly causing a race condition
/src/mongo/util/clock_source.cpp:66: MISSING_LOCK 115026 Accessing "alarmInfo->cv" without holding lock "mongo::ClockSource::waitForConditionUntil(mongo::stdx::condition_variable &, mongo::BasicLockableAdapter, mongo::Date_t, mongo::Waitable *)::AlarmInfo.mutex". Elsewhere, "_ZZN5mongo11ClockSource21waitForConditionUntilERNS_4stdx18condition_variableENS_20BasicLockableAdapterENS_6Date_tEPNS_8WaitableEE9AlarmInfo.cv" is accessed with "mongo::ClockSource::waitForConditionUntil(mongo::stdx::condition_variable &, mongo::BasicLockableAdapter, mongo::Date_t, mongo::Waitable *)::AlarmInfo.mutex" held 1 out of 2 times (1 of these accesses strongly imply that it is necessary).



 Comments   
Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ]

We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:24:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.