Mojo: Add NotifyBadMessage API

mojo/public/c/system/message_pipe.h

 // Copyright 2014 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.
 
 // This file contains types/constants and functions specific to message pipes.
 //
 // Note: This header should be compilable as C.
 
 #ifndef MOJO_PUBLIC_C_SYSTEM_MESSAGE_PIPE_H_
 #define MOJO_PUBLIC_C_SYSTEM_MESSAGE_PIPE_H_
@@ skipping 295 matching lines @@
 //
 // Returns:
 //   |MOJO_RESULT_OK| if |message| is a valid message object. |*buffer| will
 //       be updated to point to mutable message bytes.
 //   |MOJO_RESULT_INVALID_ARGUMENT| if |message| is not a valid message object.
 //
 // NOTE: A returned buffer address is always guaranteed to be 8-byte aligned.
 MOJO_SYSTEM_EXPORT MojoResult MojoGetMessageBuffer(MojoMessageHandle message,
                                                    void** buffer);  // Out
 
+// Notifies the system that a bad message was received on a message pipe,
+// according to whatever criteria the caller chooses. This ultimately notifies
+// the embedder about the bad message, and the embedder may enforce some policy
+// for dealing with the source of the message (e.g. close the pipe, terminate
+// a process, etc.)
+//
+// |message|: The message to report as bad. This must have come from a call to
+//     |MojoReadMessageNew()|.
+//
+// Returns:
+//   |MOJO_RESULT_OK| if successful.
+//   |MOJO_RESULT_INVALID_ARGUMENT| if |message| is not a valid message.

[Anand Mistry (off Chromium), 2016/06/10 10:28:20]

Add a note that the bad message callback may not be called if the source channel
has been shut down for any reason.

+MOJO_SYSTEM_EXPORT MojoResult
+MojoNotifyBadMessage(MojoMessageHandle message);
+
 #ifdef __cplusplus
 }  // extern "C"
 #endif
 
 #endif  // MOJO_PUBLIC_C_SYSTEM_MESSAGE_PIPE_H_