From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eduardo Terrell Ferrari Otubo <eterrell@redhat.com>
Cc: Eduardo Otubo <otubo@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/5] seccomp: fix hole in blocking forks
Date: Fri, 28 Jan 2022 15:42:39 +0000 [thread overview]
Message-ID: <YfQO7w9QL+LrE11D@redhat.com> (raw)
In-Reply-To: <008bee58061405c8f9fe36d8c40a62d360bd4547.camel@redhat.com>
Hi Eduardo,
You acked this series, but going through my old git branches I
just discovered that this never got merged. I guess I was assuming
you had queued it for a future PULL when you acked it.
I don't mind sending a pull request myself if you've no objections.
On Wed, Aug 04, 2021 at 10:05:38AM +0200, Eduardo Terrell Ferrari Otubo wrote:
> On Mon, 2021-08-02 at 14:02 +0100, Daniel P. Berrangé wrote:
> > 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
> >
> >
>
> Acked-by: Eduardo Otubo <otubo@redhat.com>
>
> --
> Eduardo Otubo
>
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-01-28 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 13:02 [PATCH 0/5] seccomp: fix hole in blocking forks Daniel P. Berrangé
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é [this message]
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=YfQO7w9QL+LrE11D@redhat.com \
--to=berrange@redhat.com \
--cc=eterrell@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.