From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Eduardo Otubo" <otubo@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 0/5] seccomp: fix hole in blocking forks
Date: Mon, 2 Aug 2021 14:02:58 +0100 [thread overview]
Message-ID: <20210802130303.3300108-1-berrange@redhat.com> (raw)
Blocking the 'fork' syscall on Linux is not sufficient to block the
'fork' C library function, because the latter is essentially always
implemented using the 'clone' syscall these days.
Blocking 'clone' is difficult as that also blocks pthread creation,
so it needs careful filtering.
Daniel P. Berrangé (5):
seccomp: allow action to be customized per syscall
seccomp: add unit test for seccomp filtering
seccomp: fix blocking of process spawning
seccomp: block use of clone3 syscall
seccomp: block setns, unshare and execveat syscalls
MAINTAINERS | 1 +
softmmu/qemu-seccomp.c | 282 +++++++++++++++++++++++++++++---------
tests/unit/meson.build | 4 +
tests/unit/test-seccomp.c | 269 ++++++++++++++++++++++++++++++++++++
4 files changed, 490 insertions(+), 66 deletions(-)
create mode 100644 tests/unit/test-seccomp.c
--
2.31.1
next reply other threads:[~2021-08-02 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 13:02 Daniel P. Berrangé [this message]
2021-08-02 13:02 ` [PATCH 1/5] seccomp: allow action to be customized per syscall Daniel P. Berrangé
2021-08-02 13:03 ` [PATCH 2/5] seccomp: add unit test for seccomp filtering Daniel P. Berrangé
2021-08-02 13:03 ` [PATCH 3/5] seccomp: fix blocking of process spawning Daniel P. Berrangé
2021-08-02 13:03 ` [PATCH 4/5] seccomp: block use of clone3 syscall Daniel P. Berrangé
2021-08-02 13:03 ` [PATCH 5/5] seccomp: block setns, unshare and execveat syscalls Daniel P. Berrangé
2021-08-04 8:05 ` [PATCH 0/5] seccomp: fix hole in blocking forks Eduardo Terrell Ferrari Otubo
2022-01-28 15:42 ` Daniel P. Berrangé
2022-01-31 9:07 ` Eduardo Otubo
2022-01-31 9:09 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210802130303.3300108-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=otubo@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).