Skip to content
Skip to breadcrumbs
Skip to header menu
Skip to action menu
Skip to quick search

Skip to end of banner Go to start of banner

Rec. 14. Concurrency (CON)

Skip to end of metadata

Created by Sandy Shrum, last modified by David Svoboda on Mar 15, 2022

Go to start of metadata

Information for Editors
To have a new guideline automatically listed above be sure to label it con and recommendation.

Risk Assessment Summary

Rule	Severity	Likelihood	Remediation Cost	Priority	Level
CON01-C	Low	Probable	Medium	P4	L3
CON02-C	Medium	Probable	Medium	P8	L2
CON04-C	Low	Unlikely	High	P1	L3
CON05-C	Low	Probable	High	P2	L3
CON06-C	Medium	Probable	Medium	P8	L2
CON07-C	Medium	Probable	Medium	P8	L2
CON08-C	Low	Probable	Medium	P4	L3
CON09-C	Medium	Unlikely	High	P2	L3

Related Rules and Recommendations

CON04-C. Join or detach threads even if their exit status is unimportant

CON30-C. Clean up thread-specific storage

CON31-C. Do not destroy a mutex while it is locked

CON32-C. Prevent data races when accessing bit-fields from multiple threads

CON33-C. Avoid race conditions when using library functions

CON34-C. Declare objects shared between threads with appropriate storage durations

CON35-C. Avoid deadlock by locking in a predefined order

CON37-C. Do not call signal() in a multithreaded program

CON43-C. Do not allow data races in multithreaded code

CON50-CPP. Do not destroy a mutex while it is locked

POS04-C. Avoid using PTHREAD_MUTEX_NORMAL type mutex locks

POS44-C. Do not use signals to terminate threads

POS47-C. Do not use threads that can be canceled asynchronously

POS48-C. Do not unlock or destroy another POSIX thread's mutex

POS49-C. When data must be accessed by multiple threads, provide a mutex and guarantee no adjacent data is also accessed

POS50-C. Declare objects shared between POSIX threads with appropriate storage durations

POS51-C. Avoid deadlock with POSIX threads by locking in predefined order

POS53-C. Do not use more than one mutex for concurrent waiting operations on a condition variable

WIN01-C. Do not forcibly terminate execution

2 Comments

Volker Erben
In table "Assessment Risk Summary" has no entry for CON03-C. Please add.
- Permalink
- Nov 29, 2018
Robert Schiela
Volker,
CON03-C isn't included because it's an "incomplete" recommendation.
Thanks.
- Permalink
- Mar 20, 2019