Page History

UNDER CONSTRUCTION

Both thread safety and liveness are concerns when using condition variables. The thread-safety property requires that all objects maintain consistent states in a multithreaded environment [Lea 2000]. The liveness property requires that every operation or function invocation execute to completion without interruption; for example, there is no deadlock.

Condition variables must be used inside a while loop. (see See CON54-CPP. Wrap functions that can spuriously wake up in a loop for more information.) . To guarantee liveness, programs must test the while loop condition before invoking the condition_variable::wait() member function. This early test checks whether another thread has already satisfied the condition predicate and has sent a notification. Invoking wait() after the notification has been sent results in indefinite blocking.

...

The notify_one() member function unblocks one of the threads that are blocked on the specified condition variable at the time of the call. If multiple threads are waiting on the same condition variable, the scheduler can select any of those threads to be awakened (assuming that all threads have the same priority level).

The notify_all() member function unblocks all of the threads that are blocked on the specified condition variable at the time of the call. The order in which threads execute following a call to notify_all() is unspecified. Consequently, an unrelated thread could start executing, discover that its condition predicate is satisfied, and resume execution even though it was supposed to remain dormant.

For these reasons, threads must check the condition predicate after the wait() function returns. A while loop is the best choice for checking the condition predicate both before and after invoking wait().

...

This noncompliant code example uses five threads that are intended to execute sequentially according to the step level assigned to each thread when it is created (serialized processing). The current_step currentStep variable holds the current step level and is incremented when the respective thread completes. Finally, another thread is signaled so that the next step can be executed. Each thread waits until its step level is ready, and the wait() call is wrapped inside a while loop, in compliance with CON54-CPP. Wrap functions that can spuriously wake up in a loop.

#include <condition_variable>
#include <iostream>
#include <mutex>
#include <thread>


enum { NTHREADS = 5 };


 
std::mutex mutex;
std::condition_variable cond;


void run_step(size_t my_stepmyStep) {
  static size_t current_stepcurrentStep = 0;
  std::unique_lock<std::mutex> lk(mutex);


  std::cout << "Thread " << my_stepmyStep << " has the lock" << std::endl;


  while (current_stepcurrentStep != my_stepmyStep) {
    std::cout << "Thread " << my_stepmyStep << " is sleeping..." << std::endl;
    cond.wait(lk);
    std::cout << "Thread " << my_stepmyStep << " woke up" << std::endl;
  }


  /*/ Do processing ... */
  std::cout << "Thread " << my_stepmyStep << " is processing..." << std::endl;
  current_stepcurrentStep++;


  //* Signal awaiting task */.
  cond.notify_one();


  std::cout << "Thread " << my_stepmyStep << " is exiting..." << std::endl;
}


int main(void) {
  constexpr size_t numThreads = 5;
  std::thread threads[NTHREADSnumThreads];


  /*/ Create threads */.
  for (size_t i = 0; i < NTHREADSnumThreads; ++i) {
    threads[i] = std::thread(run_step, i);
  }


  /*/ Wait for all threads to complete */.
  for (size_t i = NTHREADSnumThreads; i != 0; --i) {
    threads[i - 1].join();
  }


  return 0;
}

In this example, all threads share a single condition variable. Each thread has its own distinct condition predicate because each thread requires current_step currentStep to have a different value before proceeding. When the condition variable is signaled, any of the waiting threads can wake up. The following table illustrates a possible scenario in which the liveness property is violated. If, by chance, the notified thread is not the thread with the next step value, that thread will wait again. No additional notifications can occur, and eventually the pool of available threads will be exhausted.

Deadlock: Out-of-Sequence Step Value

This noncompliant code example violates the liveness property.

Compliant Solution (notify_all())

This compliant solution uses notify_all() to signal all waiting threads instead of a single random thread. Only the run_step() thread code from the noncompliant code example is modified, as follows:.

#include <condition_variable>
#include <iostream>
#include <mutex>
#include <thread>

std::mutex mutex;
std::condition_variable cond;


void run_step(size_t my_stepmyStep) {
  static size_t current_stepcurrentStep = 0;
  std::unique_lock<std::mutex> lk(mutex);


  std::cout << "Thread " << my_stepmyStep << " has the lock" << std::endl;


  while (current_stepcurrentStep != my_stepmyStep) {
    std::cout << "Thread " << my_stepmyStep << " is sleeping..." << std::endl;
    cond.wait(lk);
    std::cout << "Thread " << my_stepmyStep << " woke up" << std::endl;
  }


  /*/ Do processing ... */
  std::cout << "Thread " << my_stepmyStep << " is processing..." << std::endl;
  current_stepcurrentStep++;


  /*/ Signal ALL waiting tasks */.
  cond.notify_all();


  std::cout << "Thread " << my_stepmyStep << " is exiting..." << std::endl;
}
 
// ... main() unchanged ...

Awakening all threads guarantees the liveness property because each thread will execute its condition its condition predicate test, and exactly one will succeed and continue execution.

...

Another compliant solution is to use a unique condition variable for each thread (all associated with the same mutex). In this case, notify_one() wakes up only the thread that is waiting on it. This solution is more efficient than using notify_all() because only the desired thread is awakened.

Note that the condition The condition predicate of the signaled thread must be true; otherwise, a deadlock will occur.

#include <condition_variable>
#include <iostream>
#include <mutex>
#include <thread>


enum { NTHREADSconstexpr size_t numThreads = 5 };


std::mutex mutex;
std::condition_variable cond[NTHREADSnumThreads];


void run_step(size_t my_stepmyStep) {
  static size_t current_stepcurrentStep = 0;
  std::unique_lock<std::mutex> lk(mutex);


  std::cout << "Thread " << my_stepmyStep << " has the lock" << std::endl;


  while (current_stepcurrentStep != my_stepmyStep) {
    std::cout << "Thread " << my_stepmyStep << " is sleeping..." << std::endl;
    cond[my_stepmyStep].wait(lk);
    std::cout << "Thread " << my_stepmyStep << " woke up" << std::endl;
  }


  /*/ Do processing ... */
  std::cout << "Thread " << my_stepmyStep << " is processing..." << std::endl;
  current_stepcurrentStep++;


  /*/ Signal next step thread */.
  if ((my_stepmyStep + 1) < NTHREADSnumThreads) {
    cond[my_stepmyStep + 1].notify_one();
  }


  std::cout << "Thread " << my_stepmyStep << " is exiting..." << std::endl;
}

int main(void) {
  std::thread threads[NTHREADS];


  /* Create threads */
  for (size_t i = 0; i < NTHREADS; ++i) {
    threads[i] = std::thread(run_step, i);
  }


  /* Wait for all threads to complete */
 ... for (size_t i = NTHREADS; i != 0; --i) {
    threads[i-1].join();
  }


  return 0;
}main() unchanged ...

Risk Assessment

Failing to preserve the thread safety and liveness of a program when using condition variables can lead to indefinite blocking and denial of service (DoS).

Automated Detection

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

Related Guidelines

Bibliography

...

...

Image Modified Image Modified Image Modified