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

debuggerd seccomp: explain why we define PROT_READ/WRITE.

Browse source 
Add a comment explaining why we define PROT_READ/PROT_WRITE, even
though a current libminijail supports both cosntants.

Bug: http://b/73273658
Test: treehugger
Change-Id: I51c1be1b1b569e94dbc9045a90bc28221b7dc9c7
This commit is contained in:
Josh Gao 2018-02-18 23:50:19 -08:00
parent 40ecb9abf2
commit edd28f6ede
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