From: James Hogan <james.hogan@imgtec.com>
To: qemu-devel@nongnu.org
Cc: James Hogan <james.hogan@imgtec.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Eduardo Otubo <eduardo.otubo@profitbricks.com>
Subject: [Qemu-devel] [PATCH 1/2] seccomp: Whitelist cacheflush since 2.2.0 not 2.2.3
Date: Mon, 4 Apr 2016 09:29:15 +0100 [thread overview]
Message-ID: <1459758556-4557-2-git-send-email-james.hogan@imgtec.com> (raw)
In-Reply-To: <1459758556-4557-1-git-send-email-james.hogan@imgtec.com>
The cacheflush system call (found on MIPS and ARM) has been included in
the libseccomp header since 2.2.0, so include include it back to that
version. Previously it was only enabled since 2.2.3 since that is when
it was enabled properly for ARM.
This will allow seccomp support to be enabled for MIPS back to
libseccomp 2.2.0.
Signed-off-by: James Hogan <james.hogan@imgtec.com>
Cc: Eduardo Otubo <eduardo.otubo@profitbricks.com>
Cc: Aurelien Jarno <aurelien@aurel32.net>
---
qemu-seccomp.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/qemu-seccomp.c b/qemu-seccomp.c
index 2866e3c2a660..9425dac17155 100644
--- a/qemu-seccomp.c
+++ b/qemu-seccomp.c
@@ -18,9 +18,7 @@
#if SCMP_VER_MAJOR >= 3
#define HAVE_CACHEFLUSH
-#elif SCMP_VER_MAJOR == 2 && SCMP_VER_MINOR >= 3
- #define HAVE_CACHEFLUSH
-#elif SCMP_VER_MAJOR == 2 && SCMP_VER_MINOR == 2 && SCMP_VER_MICRO >= 3
+#elif SCMP_VER_MAJOR == 2 && SCMP_VER_MINOR >= 2
#define HAVE_CACHEFLUSH
#endif
--
2.4.10
next prev parent reply other threads:[~2016-04-04 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 8:29 [Qemu-devel] [PATCH 0/2] Enable seccomp on MIPS James Hogan
2016-04-04 8:29 ` James Hogan [this message]
2016-04-08 11:45 ` [Qemu-devel] [PATCH 1/2] seccomp: Whitelist cacheflush since 2.2.0 not 2.2.3 Andrew Jones
2016-04-08 11:54 ` Peter Maydell
2016-04-08 12:39 ` Andrew Jones
2016-04-08 12:49 ` Peter Maydell
2016-04-08 13:00 ` James Hogan
2016-04-04 8:29 ` [Qemu-devel] [PATCH 2/2] configure: Enable seccomp sandbox for MIPS James Hogan
2016-04-08 11:49 ` Andrew Jones
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=1459758556-4557-2-git-send-email-james.hogan@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=aurelien@aurel32.net \
--cc=eduardo.otubo@profitbricks.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).