Paul Lawrence 076b8d75be Expand Seccomp whitelist ... This seccomp failure is in the fault handler: 05-25 12:03:25.042 10201 27425 27425 F DEBUG : backtrace: 05-25 12:03:25.042 10201 27425 27425 F DEBUG : #00 pc 00015380 /data/data/redacted/files/storage/lib/libcrashsdk.so So whenever an app using this crash sdk crashes it looks like a seccomp problem. Fixing this won't stop the apps crashing, but will make the crash reports accurate and useful. So yes, the bug below is already fixed, but this issue has come back 2 or 3 times with different apps (latest is b/62874867). This change doesn't fix that crash either, but again it improves the reporting. Bug: 62090571 Test: Device boots, app still fails but no longer with SECCOMP error Change-Id: Ie0f8dc965001c8bc43f6a545b35bdcd38f006213		2017-06-23 16:50:04 +00:00
..
include	Expose seccomp table	2017-03-27 15:51:50 -07:00
Android.bp	Support all architectures in seccomp	2017-03-13 18:26:50 +00:00
arm64_policy.cpp	Add syscalls that aren't currently used to the seccomp whitelist.	2017-04-19 13:45:47 -07:00
arm_policy.cpp	Expand Seccomp whitelist	2017-06-23 16:50:04 +00:00
mips64_policy.cpp	[MIPS64] Enable necessary mips64 syscalls in seccomp whitelist	2017-05-05 15:37:11 +02:00
mips_policy.cpp	Expand Seccomp whitelist	2017-06-23 16:50:04 +00:00
seccomp_bpfs.h	Support all architectures in seccomp	2017-03-13 18:26:50 +00:00
seccomp_policy.cpp	Fix MIPS seccomp definitions for PRIMARY and SECONDARY arch	2017-05-05 15:27:58 +02:00
x86_64_policy.cpp	Add syscalls that aren't currently used to the seccomp whitelist.	2017-04-19 13:45:47 -07:00
x86_policy.cpp	Expand Seccomp whitelist	2017-06-23 16:50:04 +00:00