tequilaOS/platform_system_core
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Merge "debuggerd seccomp: explain why we define PROT_READ/WRITE." am: 665e4c1537 am: 5504477722

Browse source 
am: e1cbc97115

Change-Id: Ife944a1d1074c5e7fe6fc07c41c7931f0237ceb7
This commit is contained in:
Josh Gao 2018-02-19 10:01:24 +00:00 committed by android-build-merger
commit 72b1fb6f7b
1 changed files with 7 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
debuggerd/seccomp_policy/crash_dump.policy.def
View file

@ -33,9 +33,15 @@ rt_sigaction: 1
rt_tgsigqueueinfo: 1
#define PR_SET_VMA 0x53564d41
prctl: arg0 == PR_GET_NO_NEW_PRIVS || arg0 == PR_SET_VMA
#if 0
libminijail on vendor partitions older than P does not have constants from <sys/mman.h>.
Define the values of PROT_READ and PROT_WRITE ourselves to maintain backwards compatibility.
#else
#define PROT_READ 0x1
#define PROT_WRITE 0x2
prctl: arg0 == PR_GET_NO_NEW_PRIVS || arg0 == PR_SET_VMA
#endif
madvise: 1
mprotect: arg2 in PROT_READ|PROT_WRITE