Add UMA histograms and logging for bad IPC message handling

extensions/browser/bad_message.h

Index: extensions/browser/bad_message.h
diff --git a/extensions/browser/bad_message.h b/extensions/browser/bad_message.h
new file mode 100644
index 0000000000000000000000000000000000000000..3767834eb711b0a9a21024db81417ec65e14270c
--- /dev/null
+++ b/extensions/browser/bad_message.h
@@ -0,0 +1,41 @@
+// Copyright 2015 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef EXTENSIONS_BROWSER_BAD_MESSAGE_H_
+#define EXTENSIONS_BROWSER_BAD_MESSAGE_H_
+
+namespace content {
+class RenderProcessHost;
+}
+
+namespace extensions {
+namespace bad_message {
+
+// The browser process often chooses to terminate a renderer if it receives
+// a bad IPC message. The reasons are tracked for metrics.
+//
+// See also content/browser/bad_message.h.
+//
+// NOTE: Do not remove or reorder elements in this end. Add new entries at
+// the end. We rely on these values in histograms.

[Charlie Reis, 2015/03/18 21:37:51]

Same comments as before.

[James Cook, 2015/03/18 22:19:44]

Done.

+enum BadMessageReason {
+  EOG_BAD_ORIGIN = 0,
+  EVG_BAD_ORIGIN,
+  BH_BLOB_NOT_OWNED,
+  EH_BAD_EVENT_ID,
+  // Please add new elements here.
+
+  BAD_MESSAGE_MAX
+};
+
+// Called when the browser receives a bad IPC message from an extension process.
+// Log the event, records a histogram metric for the |reason|, and terminates
+// the process for |host|.
+void ReceivedBadMessage(content::RenderProcessHost* host,
+                        BadMessageReason reason);
+
+}  // bad_message
+}  // namespace extensions
+
+#endif  // EXTENSIONS_BROWSER_BAD_MESSAGE_H_