From: Eduardo Otubo <otubo@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, marcandre.lureau@redhat.com
Subject: [Qemu-devel] [PULL 0/2] seccomp branch queue
Date: Wed, 25 Jul 2018 16:16:08 +0200 [thread overview]
Message-ID: <20180725141610.12075-1-otubo@redhat.com> (raw)
The following changes since commit 18a398f6a39df4b08ff86ac0d38384193ca5f4cc:
Update version for v3.0.0-rc2 release (2018-07-24 22:06:31 +0100)
are available in the Git repository at:
https://github.com/otubo/qemu.git tags/pull-seccomp-20180725
for you to fetch changes up to 5b2f59307372bae13a2ff95706646674eccb65e0:
RFC: seccomp: prefer SCMP_ACT_KILL_PROCESS if available (2018-07-25 16:07:31 +0200)
----------------------------------------------------------------
pull-seccomp-20180725
----------------------------------------------------------------
Marc-André Lureau (2):
seccomp: use SIGSYS signal instead of killing the thread
RFC: seccomp: prefer SCMP_ACT_KILL_PROCESS if available
qemu-seccomp.c | 30 +++++++++++++++++++++++++++++-
1 file changed, 29 insertions(+), 1 deletion(-)
--
2.17.1
next reply other threads:[~2018-07-25 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 14:16 Eduardo Otubo [this message]
2018-07-25 14:16 ` [Qemu-devel] [PULL 1/2] seccomp: use SIGSYS signal instead of killing the thread Eduardo Otubo
2018-07-25 14:16 ` [Qemu-devel] [PULL 2/2] RFC: seccomp: prefer SCMP_ACT_KILL_PROCESS if available Eduardo Otubo
2018-07-26 10:47 ` [Qemu-devel] [PULL 0/2] seccomp branch queue Peter Maydell
2018-07-26 12:04 ` Eduardo Otubo
2018-07-26 12:05 ` Marc-André Lureau
2018-07-26 12:04 ` Marc-André Lureau
-- strict thread matches above, loose matches on Subject: below --
2014-11-11 16:21 Eduardo Otubo
2014-11-11 17:20 ` Peter Maydell
2014-11-10 14:21 Eduardo Otubo
2014-11-10 20:50 ` Peter Maydell
2014-11-11 16:27 ` Eduardo Otubo
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=20180725141610.12075-1-otubo@redhat.com \
--to=otubo@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--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).