From: Eduardo Otubo <otubo@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] seccomp: fix killing of whole process instead of thread
Date: Tue, 15 Sep 2020 12:22:35 +0200 [thread overview]
Message-ID: <20200915102235.GB5070@genji> (raw)
In-Reply-To: <20200911141832.1238636-1-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]
On 11/09/2020 - 15:18:32, Daniel P. Berrange wrote:
> Back in 2018 we introduced support for killing the whole QEMU process
> instead of just one thread, when a seccomp rule is violated:
>
> commit bda08a5764d470f101fa38635d30b41179a313e1
> Author: Marc-André Lureau <marcandre.lureau@redhat.com>
> Date: Wed Aug 22 19:02:48 2018 +0200
>
> seccomp: prefer SCMP_ACT_KILL_PROCESS if available
>
> Fast forward a year and we introduced a patch to avoid killing the
> process for resource control syscalls tickled by Mesa.
>
> commit 9a1565a03b79d80b236bc7cc2dbce52a2ef3a1b8
> Author: Daniel P. Berrangé <berrange@redhat.com>
> Date: Wed Mar 13 09:49:03 2019 +0000
>
> seccomp: don't kill process for resource control syscalls
>
> Unfortunately a logic bug effectively reverted the first commit
> mentioned so that we go back to only killing the thread, not the whole
> process.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> qemu-seccomp.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/qemu-seccomp.c b/qemu-seccomp.c
> index e0a1829b3d..8325ecb766 100644
> --- a/qemu-seccomp.c
> +++ b/qemu-seccomp.c
> @@ -136,8 +136,9 @@ static uint32_t qemu_seccomp_get_action(int set)
>
> if (qemu_seccomp(SECCOMP_GET_ACTION_AVAIL, 0, &action) == 0) {
> kill_process = 1;
> + } else {
> + kill_process = 0;
> }
> - kill_process = 0;
> }
> if (kill_process == 1) {
> return SCMP_ACT_KILL_PROCESS;
> --
> 2.26.2
>
Acked-by: Eduardo Otubo <otubo@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-15 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 14:18 [PATCH] seccomp: fix killing of whole process instead of thread Daniel P. Berrangé
2020-09-14 10:19 ` Stefan Hajnoczi
2020-09-15 10:22 ` Eduardo Otubo [this message]
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=20200915102235.GB5070@genji \
--to=otubo@redhat.com \
--cc=berrange@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).