Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler.
Number of rules (primarily dangerous function names) in C/C++ ruleset: 223
Examining data/libeatmydata-105/libeatmydata/test/eatmydatatest_largefile.c
Examining data/libeatmydata-105/libeatmydata/test/tst-key4.c
Examining data/libeatmydata-105/libeatmydata/test/fsynctest.c
Examining data/libeatmydata-105/libeatmydata/test/eatmydatatest.c
Examining data/libeatmydata-105/libeatmydata/test/tst-cancel4.c
Examining data/libeatmydata-105/libeatmydata/visibility.h
Examining data/libeatmydata-105/libeatmydata/libeatmydata.c

FINAL RESULTS:

data/libeatmydata-105/libeatmydata/libeatmydata.c:83:22:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	ASSIGN_DLSYM_OR_DIE(open);
data/libeatmydata-105/libeatmydata/libeatmydata.c:143:22:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
int LIBEATMYDATA_API open(const char* pathname, int flags, ...)
data/libeatmydata-105/libeatmydata/test/eatmydatatest.c:41:10:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
    fd = open(DATAFILENAME, O_CREAT|O_TRUNC|O_WRONLY|flag, S_IRUSR|S_IWUSR);
data/libeatmydata-105/libeatmydata/test/eatmydatatest.c:67:10:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
    fd = open(DATAFILENAME, O_CREAT|O_TRUNC|O_WRONLY, S_IRUSR|S_IWUSR);
data/libeatmydata-105/libeatmydata/test/fsynctest.c:32:6:  [2] (misc) open:
  Check when opening files - can an attacker redirect it (via symlinks),
  force the opening of special file type (e.g., device files), move things
  around to create a race condition, control its ancestors, or change its
  contents? (CWE-362).
	fd= open("fsynctestdata",O_CREAT|O_RDWR|O_SYNC|O_DSYNC|O_TRUNC, 0700);

ANALYSIS SUMMARY:

Hits = 5
Lines analyzed = 1094 in approximately 0.08 seconds (14027 lines/second)
Physical Source Lines of Code (SLOC) = 757
Hits@level = [0]  34 [1]   0 [2]   5 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  39 [1+]   5 [2+]   5 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 51.5192 [1+] 6.60502 [2+] 6.60502 [3+]   0 [4+]   0 [5+]   0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.