mirror of
https://passt.top/passt
synced 2025-05-24 02:05:33 +02:00
treewide: Suppress clang-tidy warning if we already use O_CLOEXEC
In pcap_init(), we should always open the packet capture file with O_CLOEXEC, even if we're not running in foreground: O_CLOEXEC means close-on-exec, not close-on-fork. In logfile_init() and pidfile_open(), the fact that we pass a third 'mode' argument to open() seems to confuse the android-cloexec-open checker in LLVM versions from 16 to 19 (at least). The checker is suggesting to add O_CLOEXEC to 'mode', and not in 'flags', where we already have it. Add a suppression for clang-tidy and a comment, and avoid repeating those three times by adding a new helper, output_file_open(). Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
This commit is contained in:
parent
134b4d58b4
commit
59fe34ee36
5 changed files with 20 additions and 25 deletions
6
conf.c
6
conf.c
|
@ -1194,7 +1194,11 @@ static void conf_open_files(struct ctx *c)
|
|||
if (c->mode != MODE_PASTA && c->fd_tap == -1)
|
||||
c->fd_tap_listen = tap_sock_unix_open(c->sock_path);
|
||||
|
||||
c->pidfile_fd = pidfile_open(c->pidfile);
|
||||
if (*c->pidfile) {
|
||||
c->pidfile_fd = output_file_open(c->pidfile, O_WRONLY);
|
||||
if (c->pidfile_fd < 0)
|
||||
die_perror("Couldn't open PID file %s", c->pidfile);
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue