FIO24-C. Do not open a file that is already open

Opening a file that is already open has BB. Definitions#implementation-defined behavior, according to the C Standard, 7.21.3, paragraph 8 [AA. Bibliography#ISO-IEC 9899-2011]:

Functions that open additional (nontemporary) files require a file name, which is a string. The rules for composing valid file names are implementation-defined. Whether the same file can be simultaneously open multiple times is also implementation-defined.

Some implementations do not allow multiple copies of the same file to be open at the same time. Consequently, portable code cannot depend on what will happen if this rule is violated. Even on implementations that do not outright fail to open an already-opened file, a BB. Definitions#TOCTOU (time-of-check, time-of-use) race condition exists in which the second open could operate on a different file from the first due to the file being moved or deleted (see FIO45-C. Avoid TOCTOU race conditions while accessing files for more details on TOCTOU race conditions).

Noncompliant Code Example

This noncompliant code example logs the program's state at runtime:

Because the file log is opened twice (once in main() and again in do_stuff()), this program has implementation-defined behavior.

Compliant Solution

In this compliant solution, a reference to the file pointer is passed as an argument to functions that need to perform operations on that file. This reference eliminates the need to open the same file multiple times.

Risk Assessment

Simultaneously opening a file multiple times can result in unexpected errors and nonportable behavior.

Automated Detection

Related Vulnerabilities

Search for BB. Definitions#vulnerability resulting from the violation of this rule on the CERT website.

Related Guidelines

 Bibliography