mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-08 19:33:07 +00:00
tests: Filter args2 in plugin.policy.
We don't want mprotect or mmap being called with write and execute at the same time. This policy is for a test, but still filter the arguments incase this policy is used as a starting point elsewhere. BUG=b:172212144 TEST=Kokoro passes Change-Id: I8be82a9af7e404a4eb17f5b2fbb1e6269447de11 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3942708 Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Allen Webb <allenwebb@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
This commit is contained in:
parent
2abc17423b
commit
acc0f20062
1 changed files with 2 additions and 2 deletions
|
@ -10,7 +10,7 @@ exit_group: 1
|
|||
futex: 1
|
||||
kill: 1
|
||||
lseek: 1
|
||||
mprotect: 1
|
||||
mprotect: arg2 in ~PROT_EXEC || arg2 in ~PROT_WRITE
|
||||
munmap: 1
|
||||
read: 1
|
||||
recvfrom: 1
|
||||
|
@ -39,7 +39,7 @@ getrlimit: 1
|
|||
ioctl: arg1 == 0x800454CF
|
||||
madvise: 1
|
||||
memfd_create: 1
|
||||
mmap: 1
|
||||
mmap: arg2 in ~PROT_EXEC || arg2 in ~PROT_WRITE
|
||||
open: 1
|
||||
openat: 1
|
||||
prlimit64: arg2 == 0 && arg3 != 0
|
||||
|
|
Loading…
Reference in a new issue