Commit 5357b872 by Wolfgang Bumiller

seccomp: don't ignore syscalls when there's no proxy

The container process would just hang. Signed-off-by: 's avatarWolfgang Bumiller <w.bumiller@proxmox.com>
parent 8a99ab01
...@@ -1366,17 +1366,17 @@ int seccomp_notify_handler(int fd, uint32_t events, void *data, ...@@ -1366,17 +1366,17 @@ int seccomp_notify_handler(int fd, uint32_t events, void *data,
char *cookie = conf->seccomp.notifier.cookie; char *cookie = conf->seccomp.notifier.cookie;
uint64_t req_id; uint64_t req_id;
if (listener_proxy_fd < 0) {
ERROR("No seccomp proxy registered");
return minus_one_set_errno(EINVAL);
}
ret = seccomp_notify_receive(fd, req); ret = seccomp_notify_receive(fd, req);
if (ret) { if (ret) {
SYSERROR("Failed to read seccomp notification"); SYSERROR("Failed to read seccomp notification");
goto out; goto out;
} }
if (listener_proxy_fd < 0) {
ERROR("No seccomp proxy registered");
return minus_one_set_errno(EINVAL);
}
/* remember the ID in case we receive garbage from the proxy */ /* remember the ID in case we receive garbage from the proxy */
resp->id = req_id = req->id; resp->id = req_id = req->id;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment