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 033152a66a278d302df8d095c8504b061b94e47d..1a70774a74c4c9217d6fb886e12cdf05947c6a76 100644 (file)
--- 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
 };