Skip to main content
assistive.skiplink.to.breadcrumbs
assistive.skiplink.to.header.menu
assistive.skiplink.to.action.menu
assistive.skiplink.to.quick.search

Rule 14. Concurrency (CON)

Created by Martin Sebor, last modified by David Svoboda on May 20, 2025

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

Risk Assessment Summary

Rule	Severity	Likelihood	Detectable	Repairable	Priority	Level
CON30-C	Medium	Unlikely	No	No	P2	L3
CON31-C	Medium	Probable	No	No	P4	L3
CON32-C	Medium	Probable	No	No	P4	L3
CON33-C	Medium	Probable	No	No	P4	L3
CON34-C	Medium	Probable	No	No	P4	L3
CON35-C	Low	Probable	No	No	P2	L3
CON36-C	Low	Unlikely	Yes	No	P2	L3
CON37-C	Low	Probable	Yes	No	P4	L3
CON38-C	Low	Unlikely	No	Yes	P2	L3
CON39-C	Low	Likely	No	No	P3	L3
CON40-C	Medium	Probable	Yes	No	P8	L2
CON41-C	Low	Unlikely	Yes	No	P2	L3
CON43-C	Medium	Probable	No	No	P4	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

1 Comment

Martin Sebor
I used the con label to mark concurrency-related practices that are currently in section 50. POSIX (POS) but that are not, in my view, specific to POSIX threads. For now they appear on this page as well as on the page for section 50. I propose we change the ids of all these guidelines to CON##-C and remove them from section 50. If there are no objections I will go ahead with this change in the next few days.
- Permalink
- May 12, 2010