From: Eduardo Otubo <otubo@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org, eskultet@redhat.com, kraxel@redhat.com,
berrange@redhat.com, gschafer@gmail.com
Subject: Re: [Qemu-devel] [PATCH] seccomp: allow sched_setscheduler() with SCHED_IDLE policy
Date: Wed, 11 Jul 2018 16:48:55 +0200 [thread overview]
Message-ID: <20180711144855.GE14423@vader> (raw)
In-Reply-To: <20180710145557.12902-1-marcandre.lureau@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2514 bytes --]
On 10/07/2018 - 16:55:57, Marc-André Lureau wrote:
> Current and upcoming mesa releases rely on a shader disk cash. It uses
> a thread job queue with low priority, set with
> sched_setscheduler(SCHED_IDLE). However, that syscall is rejected by
> the "resourcecontrol" seccomp qemu filter.
>
> Since it should be safe to allow lowering thread priority, let's allow
> scheduling thread to idle policy.
>
> Related to:
> https://bugzilla.redhat.com/show_bug.cgi?id=1594456
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> qemu-seccomp.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-seccomp.c b/qemu-seccomp.c
> index 148e4c6f24..9cd8eb9499 100644
> --- a/qemu-seccomp.c
> +++ b/qemu-seccomp.c
> @@ -34,6 +34,12 @@
> struct QemuSeccompSyscall {
> int32_t num;
> uint8_t set;
> + uint8_t narg;
> + const struct scmp_arg_cmp *arg_cmp;
> +};
> +
> +const struct scmp_arg_cmp sched_setscheduler_arg[] = {
> + SCMP_A1(SCMP_CMP_NE, SCHED_IDLE)
> };
>
> static const struct QemuSeccompSyscall blacklist[] = {
> @@ -92,7 +98,8 @@ static const struct QemuSeccompSyscall blacklist[] = {
> { SCMP_SYS(setpriority), QEMU_SECCOMP_SET_RESOURCECTL },
> { SCMP_SYS(sched_setparam), QEMU_SECCOMP_SET_RESOURCECTL },
> { SCMP_SYS(sched_getparam), QEMU_SECCOMP_SET_RESOURCECTL },
> - { SCMP_SYS(sched_setscheduler), QEMU_SECCOMP_SET_RESOURCECTL },
> + { SCMP_SYS(sched_setscheduler), QEMU_SECCOMP_SET_RESOURCECTL,
> + ARRAY_SIZE(sched_setscheduler_arg), sched_setscheduler_arg },
> { SCMP_SYS(sched_getscheduler), QEMU_SECCOMP_SET_RESOURCECTL },
> { SCMP_SYS(sched_setaffinity), QEMU_SECCOMP_SET_RESOURCECTL },
> { SCMP_SYS(sched_getaffinity), QEMU_SECCOMP_SET_RESOURCECTL },
> @@ -118,7 +125,8 @@ static int seccomp_start(uint32_t seccomp_opts)
> continue;
> }
>
> - rc = seccomp_rule_add(ctx, SCMP_ACT_KILL, blacklist[i].num, 0);
> + rc = seccomp_rule_add_array(ctx, SCMP_ACT_KILL, blacklist[i].num,
> + blacklist[i].narg, blacklist[i].arg_cmp);
> if (rc < 0) {
> goto seccomp_return;
> }
> --
> 2.18.0.129.ge3331758f1
>
Acked-by: Eduardo Otubo <otubo@redhat.com>
Patch looks safe enough for me. If everyone else is OK with this I'll send a
pull-request tomorrow morning.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-07-11 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 14:55 [Qemu-devel] [PATCH] seccomp: allow sched_setscheduler() with SCHED_IDLE policy Marc-André Lureau
2018-07-11 14:48 ` Eduardo Otubo [this message]
2018-07-16 9:35 ` 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=20180711144855.GE14423@vader \
--to=otubo@redhat.com \
--cc=berrange@redhat.com \
--cc=eskultet@redhat.com \
--cc=gschafer@gmail.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@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).