Add --enable-seccomp-filter-sandbox to about:flags on Android.

content/renderer/renderer_main_platform_delegate_android.cc

Index: content/renderer/renderer_main_platform_delegate_android.cc
diff --git a/content/renderer/renderer_main_platform_delegate_android.cc b/content/renderer/renderer_main_platform_delegate_android.cc
index 3cafcca7151c5b7f1a4bcf54a14778505a0b85f0..de7616b010dbe591196437857768fc352dcc992d 100644
--- a/content/renderer/renderer_main_platform_delegate_android.cc
+++ b/content/renderer/renderer_main_platform_delegate_android.cc
@@ -35,6 +35,12 @@ bool RendererMainPlatformDelegate::EnableSandbox() {
           switches::kEnableSeccompFilterSandbox)) {
     return true;
   }
+  if (!sandbox::SandboxBPF::SupportsSeccompSandbox(

[jln (very slow on Chromium), 2014/11/26 22:29:55]

This is especially problematic since we don't have a chrome://sandbox on
Android.

I imagine you don't want this to be fatal because there wouldn't be an easy way
to revert the flag?

[Robert Sesek, 2014/11/26 22:32:25]

Right, if about:flags weren't WebUI I wouldn't have done this.

[no sievers, 2014/11/26 23:35:11]

Yea you'd have to go to Settings -> Apps and erase the app user data.

+          sandbox::SandboxBPF::SeccompLevel::MULTI_THREADED)) {
+    LOG(WARNING) << "Seccomp-BPF sandbox enabled without kernel support. "

[jln (very slow on Chromium), 2014/11/26 22:29:55]

LOG(ERROR) at least?

+                 << "Ignoring flag and proceeding without seccomp sandbox.";
+    return true;
+  }
 
   sandbox::SandboxBPF sandbox;
   sandbox.SetSandboxPolicy(new SandboxBPFBasePolicyAndroid());