From: Martin Mares <mj@ucw.cz>
Date: Sun, 24 Aug 2008 21:08:40 +0000 (+0200)
Subject: The mmap2() syscall is available even in the strict mode.
X-Git-Tag: python-dummy-working~140
X-Git-Url: http://mj.ucw.cz/gitweb/?a=commitdiff_plain;h=33ed1988770363005a821902ed6094e47c023cf4;p=moe.git

The mmap2() syscall is available even in the strict mode.

There is no reason to handle it differently from mmap().
---

diff --git a/box/box.c b/box/box.c
index 033152a..1a70774 100644
--- a/box/box.c
+++ b/box/box.c
@@ -262,6 +262,7 @@ static unsigned char syscall_action[NUM_ACTIONS] = {
     S(fcntl) = A_YES,
     S(fcntl64) = A_YES,
     S(mmap) = A_YES,
+    S(mmap) = A_YES,
     S(munmap) = A_YES,
     S(ioctl) = A_YES,
     S(uname) = A_YES,
@@ -308,7 +309,6 @@ static unsigned char syscall_action[NUM_ACTIONS] = {
     S(rt_sigtimedwait) = A_YES | A_LIBERAL,
     S(rt_sigqueueinfo) = A_YES | A_LIBERAL,
     S(rt_sigsuspend) = A_YES | A_LIBERAL,
-    S(mmap2) = A_YES | A_LIBERAL,
     S(_sysctl) = A_YES | A_LIBERAL,
 #undef S
 };