ChildProcessSecurityPolicy::CanAccessDataForOrigin workaround to suppress bad kills

ChildProcessSecurityPolicy::CanAccessDataForOrigin workaround to suppress bad kills

crbug.com/600441 apparently involves a race where we check
ChildProcessSecurityPolicy for a process_id that it doesn't know -- probably
a renderer shutdown race. Returning true instead of false here is a temporary
workaround to suppress these bad kills, which are affecting the non-oopif
user population. This is a tolerable short-term behavior as far as security
is concerned, since CanAccessDataForOrigin is only meant to offer meaningful
protection in --site-per-process mode, which is not yet launched.

BUG=600441
Review-Url: https://codereview.chromium.org/1945173003
Cr-Commit-Position: refs/heads/master@{#391678}
(cherry picked from commit 470457d18d306a0f32ea548ad111371c24e509e1)

Committed: https://chromium.googlesource.com/chromium/src/+/36602ec1b414e65ddd7c55d4a27f167174825d9e

[ncarter (slow), 2016-05-05 22:47:04]

Description was changed from

==========
ChildProcessSecurityPolicy::CanAccessDataForOrigin workaround to suppress bad
kills

crbug.com/600441 apparently involves a race where we check
ChildProcessSecurityPolicy for a process_id that it doesn't know -- probably
a renderer shutdown race. Returning true instead of false here is a temporary
workaround to suppress these bad kills, which are affecting the non-oopif
user population. This is a tolerable short-term behavior as far as security
is concerned, since CanAccessDataForOrigin is only meant to offer meaningful
protection in --site-per-process mode, which is not yet launched.

BUG=600441

Review-Url: https://codereview.chromium.org/1945173003
Cr-Commit-Position: refs/heads/master@{#391678}
(cherry picked from commit 470457d18d306a0f32ea548ad111371c24e509e1)
==========

to

==========
ChildProcessSecurityPolicy::CanAccessDataForOrigin workaround to suppress bad
kills

crbug.com/600441 apparently involves a race where we check
ChildProcessSecurityPolicy for a process_id that it doesn't know -- probably
a renderer shutdown race. Returning true instead of false here is a temporary
workaround to suppress these bad kills, which are affecting the non-oopif
user population. This is a tolerable short-term behavior as far as security
is concerned, since CanAccessDataForOrigin is only meant to offer meaningful
protection in --site-per-process mode, which is not yet launched.

BUG=600441

Review-Url: https://codereview.chromium.org/1945173003
Cr-Commit-Position: refs/heads/master@{#391678}
(cherry picked from commit 470457d18d306a0f32ea548ad111371c24e509e1)

Committed:
https://chromium.googlesource.com/chromium/src/+/36602ec1b414e65ddd7c55d4a27f...
==========

[ncarter (slow), 2016-05-05 22:47:06]

Committed patchset #1 (id:1) manually as
36602ec1b414e65ddd7c55d4a27f167174825d9e.