Cleanup GpuMemoryBuffer

content/common/gpu/client/gpu_memory_buffer_impl_ozone.cc

Index: content/common/gpu/client/gpu_memory_buffer_impl_ozone.cc
diff --git a/content/common/gpu/client/gpu_memory_buffer_impl_ozone.cc b/content/common/gpu/client/gpu_memory_buffer_impl_ozone.cc
index 7420444ac402fb68755b9931482bb9ca424b953c..9e6b5e623f6065f17f1198fd7430ba1711ba2208 100644
--- a/content/common/gpu/client/gpu_memory_buffer_impl_ozone.cc
+++ b/content/common/gpu/client/gpu_memory_buffer_impl_ozone.cc
@@ -60,7 +60,18 @@ void GpuMemoryBufferImpl::AllocateForChildProcess(
 void GpuMemoryBufferImpl::DeletedByChildProcess(
     gfx::GpuMemoryBufferType type,
     const gfx::GpuMemoryBufferId& id,
-    base::ProcessHandle child_process) {
+    base::ProcessHandle child_process,
+    uint32_t sync_point) {
+  switch (type) {
+    case gfx::SHARED_MEMORY_BUFFER:
+      break;
+    case gfx::OZONE_NATIVE_BUFFER:
+      GpuMemoryBufferImplOzoneNativeBuffer::DeletedByChildProcess(id,
+                                                                  sync_point);

[piman, 2014/11/03 19:36:34]

What prevents an arbitrary renderer from destroying a memory buffer belonging to
another process? Should we pass through the child id (as opposed to the
child_process which I don't think is useful), and check against id.secondary_id?
(On a per-type basis, I suppose?)

[alexst (slow to review), 2014/11/03 20:29:17]

Good point, AllocateForChildProcess takes both ProcessHandle and
child_client_id, so I added child_client_id here for symmetry and introduced the
check.

+      break;
+    default:
+      LOG(ERROR) << "Unexpected GpuMemoryBufferType";
+  }
 }
 
 // static