[mojo-edk] Expose notification source to MojoWatch callbacks

mojo/edk/system/data_pipe_consumer_dispatcher.cc

 // Copyright 2013 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.
 
 #include "mojo/edk/system/data_pipe_consumer_dispatcher.h"
 
 #include <stddef.h>
 #include <stdint.h>
 
 #include <algorithm>
@@ skipping 477 matching lines @@
 void DataPipeConsumerDispatcher::NotifyRead(uint32_t num_bytes) {
   DVLOG(1) << "Data pipe consumer " << pipe_id_ << " notifying peer: "
            << num_bytes << " bytes read. [control_port="
            << control_port_.name() << "]";
 
   SendDataPipeControlMessage(node_controller_, control_port_,
                              DataPipeCommand::DATA_WAS_READ, num_bytes);
 }
 
 void DataPipeConsumerDispatcher::OnPortStatusChanged() {
-  // This has to be outside |lock_| because the watch callback can call data
-  // pipe functions which then try to acquire |lock_|.
-  RequestContext request_context;
+  DCHECK(RequestContext::current());
 
   base::AutoLock lock(lock_);
 
   // We stop observing the control port as soon it's transferred, but this can
   // race with events which are raised right before that happens. This is fine
   // to ignore.
   if (transferred_)
     return;
 
   DVLOG(1) << "Control port status changed for data pipe producer " << pipe_id_;
@@ skipping 52 matching lines @@
   }
 
   if (peer_closed_ != was_peer_closed ||
       bytes_available_ != previous_bytes_available) {
     awakable_list_.AwakeForStateChange(GetHandleSignalsStateNoLock());
   }
 }
 
 }  // namespace edk
 }  // namespace mojo