From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109695] qemu using spice gl and sandbox resourcecontrol=deny crashes with SIGSYS on radeonsi
Date: Sat, 02 Mar 2019 11:36:02 +0000 [thread overview]
Message-ID: <bug-109695-502-pCGALxRxc8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109695-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1070 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109695
--- Comment #9 from Ahzo@tutanota.com ---
(In reply to Daniel P. Berrange from comment #3)
> (In reply to Ahzo from comment #2)
> > To check for the availability of the syscall, one can try it in a child
> > process and see if the child is terminated by a signal, e.g. like this:
>
> Afraid not, QEMU's seccomp filter blocks use of fork() too :-)
Maybe it should, at least when using the spawn=deny option, but currently it
doesn't. That option only blocks the fork, vfork and execve syscalls, but
glibc's fork() function uses the clone syscall, and thus continues to work.
However, that behavior might be different when using other C library
implementations, so it wouldn't be correct to rely on this.
One could use clone() instead of fork(), but future versions of qemu might
block the clone syscall, as well.
Unfortunately, I'm not aware of a proper solution for this bug short of adding
a new API to the kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2028 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-02 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 20:12 [Bug 109695] qemu using spice gl and sandbox resourcecontrol=deny crashes with SIGSYS on radeonsi bugzilla-daemon
2019-02-20 21:30 ` bugzilla-daemon
2019-02-21 17:15 ` bugzilla-daemon
2019-02-27 14:42 ` bugzilla-daemon
2019-02-27 14:45 ` bugzilla-daemon
2019-02-27 14:54 ` bugzilla-daemon
2019-02-27 23:14 ` bugzilla-daemon
2019-02-28 0:15 ` bugzilla-daemon
2019-02-28 10:21 ` bugzilla-daemon
2019-02-28 13:08 ` bugzilla-daemon
2019-03-02 11:36 ` bugzilla-daemon [this message]
2019-03-06 18:17 ` bugzilla-daemon
2019-03-11 17:04 ` bugzilla-daemon
2019-04-02 13:03 ` bugzilla-daemon
2019-04-13 13:50 ` bugzilla-daemon
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=bug-109695-502-pCGALxRxc8@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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).