Call EnsureNSSInit in SSLClientSocket::GetMaxSupportedSSLVersion.

Call EnsureNSSInit in SSLClientSocket::GetMaxSupportedSSLVersion.

EnsureNSSInit needs to query PK11_TokenExists, so NSS needs to be initialized
first.

BUG=447461
Committed: https://crrev.com/34f538287c2e6d1a9385cb8c9163185560613cda
Cr-Commit-Position: refs/heads/master@{#311132}

[davidben, 2015-01-09 15:53:58]

davidben@chromium.org changed reviewers:
+ rsleevi@chromium.org

[davidben, 2015-01-09 15:53:58]

I had it call EnsureNSSInit rather than EnsureNSSSSLInit because I don't think
code needs the SSL stack initialized. Just the crypto bits.

[Ryan Sleevi, 2015-01-09 21:09:20]

The CQ bit was checked by rsleevi@chromium.org

[Ryan Sleevi, 2015-01-09 21:09:20]

lgtm

[commit-bot: I haz the power, 2015-01-09 21:10:00]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/845753002/1

[commit-bot: I haz the power, 2015-01-10 00:58:54]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-01-10 00:58:55]

Try jobs failed on following builders:
  linux_chromium_rel_ng on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[davidben, 2015-01-12 19:07:22]

Unfortunately, that one wasn't a flake. Now that SSLConfig's constructor wants
to call SSLClientSocket::GetMaxSupportedSSLVersion(), we can't initialize an
SSLConfig as a global in tests on the NSS port. Ryan, is this still good?

[Ryan Sleevi, 2015-01-12 20:10:25]

Yeah, that was bad of those tests. LGTM.

[davidben, 2015-01-12 20:17:08]

The CQ bit was checked by davidben@chromium.org

[commit-bot: I haz the power, 2015-01-12 20:17:52]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/845753002/40001

[commit-bot: I haz the power, 2015-01-12 21:14:16]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-01-12 21:14:18]

Failed to apply patch for build/sanitizers/tsan_suppressions.cc:
While running git apply --index -3 -p1;
  error: patch failed: build/sanitizers/tsan_suppressions.cc:309
  Falling back to three-way merge...
  Applied patch to 'build/sanitizers/tsan_suppressions.cc' with conflicts.
  U build/sanitizers/tsan_suppressions.cc

Patch:       build/sanitizers/tsan_suppressions.cc
Index: build/sanitizers/tsan_suppressions.cc
diff --git a/build/sanitizers/tsan_suppressions.cc
b/build/sanitizers/tsan_suppressions.cc
index
42c71b1a488dfa6292d2426b73decf365dc8ee78..78c8b612b1a552676f04e9c5eb55f783ec96517f
100644
--- a/build/sanitizers/tsan_suppressions.cc
+++ b/build/sanitizers/tsan_suppressions.cc
@@ -309,9 +309,6 @@ char kTSanDefaultSuppressions[] =
 // https://code.google.com/p/skia/issues/detail?id=3294
 "race:SkBaseMutex::acquire\n"
 
-// https://crbug.com/447461
-"race:net::SSLConfig::SSLConfig\n"
-
 // End of suppressions.
 ;  // Please keep this semicolon.

[commit-bot: I haz the power, 2015-01-12 21:14:41]

The CQ bit was unchecked by commit-bot@chromium.org

[davidben, 2015-01-12 21:33:54]

The CQ bit was checked by davidben@chromium.org

[commit-bot: I haz the power, 2015-01-12 21:35:27]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/845753002/60001

[commit-bot: I haz the power, 2015-01-12 22:41:50]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2015-01-12 22:42:49]

Patchset 4 (id:??) landed as
https://crrev.com/34f538287c2e6d1a9385cb8c9163185560613cda
Cr-Commit-Position: refs/heads/master@{#311132}