Use process_singleton_linux on Mac.

chrome/browser/process_singleton_posix.cc

Index: chrome/browser/process_singleton_posix.cc
diff --git a/chrome/browser/process_singleton_linux.cc b/chrome/browser/process_singleton_posix.cc
similarity index 98%
rename from chrome/browser/process_singleton_linux.cc
rename to chrome/browser/process_singleton_posix.cc
index 54d7db296f329d29016c8f5ba35d64bbefadd778..0fff4d61484127477565007b0d80e96ca51a75cc 100644
--- a/chrome/browser/process_singleton_linux.cc
+++ b/chrome/browser/process_singleton_posix.cc
@@ -74,7 +74,6 @@
 #include "base/threading/platform_thread.h"
 #include "base/time/time.h"
 #include "base/timer/timer.h"
-#include "chrome/browser/ui/process_singleton_dialog_linux.h"
 #include "chrome/common/chrome_constants.h"
 #include "content/public/browser/browser_thread.h"
 #include "grit/chromium_strings.h"
@@ -82,6 +81,10 @@
 #include "net/base/net_util.h"
 #include "ui/base/l10n/l10n_util.h"
 
+#if defined(OS_LINUX)
+#include "chrome/browser/ui/process_singleton_dialog_linux.h"
+#endif
+
 #if defined(TOOLKIT_VIEWS) && !defined(OS_CHROMEOS)
 #include "ui/views/linux_ui/linux_ui.h"
 #endif
@@ -298,14 +301,21 @@ bool DisplayProfileInUseError(const base::FilePath& lock_path,
                               const std::string& hostname,
                               int pid) {
   base::string16 error = l10n_util::GetStringFUTF16(
-      IDS_PROFILE_IN_USE_LINUX,
+      IDS_PROFILE_IN_USE_POSIX,
       base::IntToString16(pid),
       base::ASCIIToUTF16(hostname));
+  LOG(ERROR) << base::SysWideToNativeMB(base::UTF16ToWide(error)).c_str();
+  if (!g_disable_prompt) {
+#if defined(OS_LINUX)
   base::string16 relaunch_button_text = l10n_util::GetStringUTF16(
       IDS_PROFILE_IN_USE_LINUX_RELAUNCH);
-  LOG(ERROR) << base::SysWideToNativeMB(base::UTF16ToWide(error)).c_str();
-  if (!g_disable_prompt)
-    return ShowProcessSingletonDialog(error, relaunch_button_text);
+  return ShowProcessSingletonDialog(error, relaunch_button_text);

[Scott Hess - ex-Googler, 2014/04/18 20:51:33]

Indentation is wrong in here.  I think having the #if/#endif outside the if()
block entirely would be cleaner.

Actually - it would be even cleaner to have:

if (g_disable_prompt)
  return false;

Then put the other cases below that, ending with:

NOTREACHED()
return false;

[jackhou1, 2014/04/24 02:34:54]

Done.

+#endif
+#if defined(OS_MACOSX)

[Scott Hess - ex-Googler, 2014/04/18 20:51:33]

I think #elif defined(OS_MACOSX) would make sense, here, to clarify that these
are mutually-exclusive.

[jackhou1, 2014/04/24 02:34:54]

Done.

+  // On Mac, always usurp the lock.
+  return true;
+#endif
+  }

[tapted, 2014/04/17 08:36:14]

should this closing paren be before the #if?

[jackhou1, 2014/04/24 02:34:54]

It matches with the "if (!g_disable_prompt) {", but that's changed now.

   return false;
 }
 
@@ -895,9 +905,21 @@ bool ProcessSingleton::Create() {
     LOG(ERROR) << "Failed to create socket directory.";
     return false;
   }
+
+  // Check that the directory was created with the correct permissions.
+  int dir_mode = 0;
+  if (!base::GetPosixFilePermissions(socket_dir_.path(), &dir_mode) ||
+      dir_mode != base::FILE_PERMISSION_USER_MASK) {

[mattm, 2014/04/17 21:44:55]

Should log an error here?

[Scott Hess - ex-Googler, 2014/04/18 20:51:33]

As long as it doesn't cruft up buildbot or other logs.  I'm not really sure what
good any logging in here will do, as the users who's systems are messed up won't
see the logs or won't understand what to do about it.

That said, is this a security check, or a sanity check?  I can't really think of
how the create can succeed but this can fail, which implies to me that you're
checking for a race condition.  In that case, it should be expected to never
happen, so I think you should CHECK() or something, rather than masking it.

[jackhou1, 2014/04/24 02:34:54]

We don't want to create a socket in an unsafe directory. Changed this to a CHECK
with message.

+    NOTREACHED();
+    return false;
+  }
+
   // Setup the socket symlink and the two cookies.
   base::FilePath socket_target_path =
       socket_dir_.path().Append(chrome::kSingletonSocketFilename);
+  // Check that socket_target_path is short enough for a Unix domain socket.
+  DCHECK_GT(104u, socket_target_path.value().length());

[tapted, 2014/04/17 08:36:14]

This might only make sense on Mac, where the string length of
NSTemporaryDirectory() is somewhat predictable. Not sure if Linux makes many
guarantees about $TMP.

[mattm, 2014/04/17 21:44:55]

SetupSocket already has a CHECK() of the path length, does having a similar
dcheck here add anything?
Also shouldn't use a magic number.

[Scott Hess - ex-Googler, 2014/04/18 20:51:33]

I would think that would be why you'd want the check, because if it's too long
it will break the Unix domain socket.

I think it would be reasonable to just have a more practical check, that the
socket creation doesn't return ETOOLONG or whatever error it returns in that
case.

[jackhou1, 2014/04/24 02:34:54]

You're right, the check in SetupSocketAddr does the same thing.

+
   base::FilePath cookie(GenerateCookie());
   base::FilePath remote_cookie_path =
       socket_dir_.path().Append(chrome::kSingletonCookieFilename);