Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit edd28f6e authored by Josh Gao's avatar Josh Gao
Browse files

debuggerd seccomp: explain why we define PROT_READ/WRITE. 

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
parent 40ecb9ab

debuggerd/seccomp_policy/crash_dump.policy.def

+7 −1
Original line number Diff line number Diff line
@@ -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