Take a Profile when adding an incident to the incident reporting service.

chrome/browser/safe_browsing/incident_reporting/binary_integrity_analyzer.cc

 // 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.
 
 #include "chrome/browser/safe_browsing/incident_reporting/binary_integrity_analyzer.h"
 
 #include <string>
 
 #include "base/bind.h"
 #include "base/callback.h"
@@ skipping 60 matching lines @@
     // Only create a report if the signature is untrusted.
     if (!signature_info->trusted()) {
       scoped_ptr<ClientIncidentReport_IncidentData_BinaryIntegrityIncident>
           incident(
               new ClientIncidentReport_IncidentData_BinaryIntegrityIncident());
 
       incident->set_file_basename(binary_path.BaseName().AsUTF8Unsafe());
       incident->set_allocated_signature(signature_info.release());
 
       // Send the report.
-      callback.Run(make_scoped_ptr(
-          new BinaryIntegrityIncident(incident.Pass())));
+      callback.Run(nullptr, make_scoped_ptr(
+                                new BinaryIntegrityIncident(incident.Pass())));

[robertshield, 2015/01/30 21:04:52]

What do you think about having two types of callbacks, one that takes a Profile
and one that doesn't?

[grt (UTC plus 2), 2015/01/30 21:16:29]

Yeah, I thought about that. I wonder if an interface is better than two
callbacks... Will consider on Monday.

     }
   }
 }
 
 #if !defined(OS_WIN)
 std::vector<base::FilePath> GetCriticalBinariesPath() {
   return std::vector<base::FilePath>();
 }
 #endif  // !defined(OS_WIN)
 
 }  // namespace safe_browsing