SkColorSpace::NewICC fix integer overflow caught by fuzzer

SkColorSpace::NewICC fix integer overflow caught by fuzzer

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2053683002

Committed: https://skia.googlesource.com/skia/+/8c5424cb77f842113213c52854b17f14f7f3881d

[msarett, 2016-06-09 13:10:05]

Description was changed from

==========
SkColorSpace::NewICC fix integer overflow caught by fuzzer

BUG=skia:
==========

to

==========
SkColorSpace::NewICC fix integer overflow caught by fuzzer

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2053683002
==========

[msarett, 2016-06-09 13:11:40]

Patchset #1 (id:1) has been deleted

[msarett, 2016-06-09 13:12:26]

msarett@google.com changed reviewers:
+ kjlubick@google.com

[msarett, 2016-06-09 13:14:42]

I've verified that this fixes the set of test cases posted on Drive.

[kjlubick, 2016-06-09 13:17:05]

lgtm

[msarett, 2016-06-09 13:17:49]

The CQ bit was checked by msarett@google.com

[commit-bot: I haz the power, 2016-06-09 13:17:54]

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

[commit-bot: I haz the power, 2016-06-09 13:33:21]

Description was changed from

==========
SkColorSpace::NewICC fix integer overflow caught by fuzzer

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2053683002
==========

to

==========
SkColorSpace::NewICC fix integer overflow caught by fuzzer

BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2053683002

Committed:
https://skia.googlesource.com/skia/+/8c5424cb77f842113213c52854b17f14f7f3881d
==========

[commit-bot: I haz the power, 2016-06-09 13:33:22]

Committed patchset #1 (id:20001) as
https://skia.googlesource.com/skia/+/8c5424cb77f842113213c52854b17f14f7f3881d

[reed1, 2016-06-09 13:42:40]

reed@google.com changed reviewers:
+ bsalomon@google.com, mtklein@google.com, reed@google.com, scroggo@google.com

[reed1, 2016-06-09 13:42:41]

Seems like we have (separately) writing utilities to perform "safe" math on
size_t multiple times in multiple files... Can we collect them so that the next
N fuzzer fixes can go faster (and be more readable)?