CertC-POS

POSIX

Nested Rules

CertC-POS30

Use the readlink() function properly

CertC-POS34

Do not call putenv() with a pointer to an automatic variable as the argument

CertC-POS35

Avoid race conditions while checking for the existence of a symbolic link

CertC-POS36

Observe correct revocation order while relinquishing privileges

CertC-POS37

Ensure that privilege relinquishment is successful

CertC-POS38

Beware of race conditions when using fork and file descriptors

CertC-POS39

Use the correct byte ordering when transferring data between systems

CertC-POS44

Do not use signals to terminate threads

CertC-POS47

Do not use threads that can be canceled asynchronously

CertC-POS48

Do not unlock or destroy another POSIX thread’s mutex

CertC-POS49

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

CertC-POS50

Declare objects shared between POSIX threads with appropriate storage durations

CertC-POS51

Avoid deadlock with POSIX threads by locking in predefined order

CertC-POS52

Do not perform operations that can block while holding a POSIX lock

CertC-POS53

Do not use more than one mutex for concurrent waiting operations on a condition variable

CertC-POS54

Detect and handle POSIX library errors

Options