aboutgitcodebugslistschat
path: root/test
diff options
context:
space:
mode:
authorStefano Brivio <sbrivio@redhat.com>2022-11-14 23:00:27 +0100
committerStefano Brivio <sbrivio@redhat.com>2022-11-16 15:11:13 +0100
commitb27d6d121c8fad94658bbcf433e99f7fff542550 (patch)
treecd63cf53f155a67f02d60ed9c96c1a8f599aba2f /test
parent5f7446501052233e472cb1e6b3f403c7923ce90a (diff)
downloadpasst-b27d6d121c8fad94658bbcf433e99f7fff542550.tar
passt-b27d6d121c8fad94658bbcf433e99f7fff542550.tar.gz
passt-b27d6d121c8fad94658bbcf433e99f7fff542550.tar.bz2
passt-b27d6d121c8fad94658bbcf433e99f7fff542550.tar.lz
passt-b27d6d121c8fad94658bbcf433e99f7fff542550.tar.xz
passt-b27d6d121c8fad94658bbcf433e99f7fff542550.tar.zst
passt-b27d6d121c8fad94658bbcf433e99f7fff542550.zip
arp, tap, util: Don't use perror() after seccomp filter is installed
If stderr is closed, after we fork to background, glibc's implementation of perror() will try to re-open it by calling dup(), upon which the seccomp filter causes the process to terminate, because dup() is not included in the list of allowed syscalls. Replace perror() calls that might happen after isolation_postfork(). We could probably replace all of them, but early ones need a bit more attention as we have to check whether log.c functions work in early stages. Signed-off-by: Stefano Brivio <sbrivio@redhat.com> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions