ipc: Allow attachment brokering for shared memory handles.

ipc: Implement attachment brokering for SharedMemoryHandle on Windows.

Each SharedMemoryHandle is backed by a HANDLE, and that HANDLE is associated
with a specific process. If a SharedMemoryHandle passed to IPC is associated
with the current process, the IPC stack will automatically broker the handle to
the destination process.

This functionality has been implemented and tested, but is not yet turned on,
because there are a couple of Windows-specific Chrome IPC messages that
intentionally pass a HANDLE associated with another process. I will write a
follow-up CL that turns on this functionality, and removes those IPC messages.

BUG=493414
Committed: https://crrev.com/3d87ecf7392672dbd0aaabc042caf29cf63631cf
Cr-Commit-Position: refs/heads/master@{#368244}

[erikchen, 2015-12-04 01:59:42]

Description was changed from

==========
ipc: Allow attachment brokering for shared memory handles.

Each shared memory handle is backed by a HANDLE, and that HANDLE is associated
with a specific process. If a shared memory handle passed to the Chrome IPC
stack is associated with the current process, the IPC stack will automatically
broker the handle to the destination process.

BUG=493414
==========

to

==========
ipc: Allow attachment brokering for shared memory handles.

Each shared memory handle is backed by a HANDLE, and that HANDLE is associated
with a specific process. If a shared memory handle passed to the Chrome IPC
stack is associated with the current process, the IPC stack will automatically
broker the handle to the destination process.

BUG=493414
==========

[erikchen, 2015-12-04 02:00:48]

erikchen@chromium.org changed reviewers:
+ tsepez@chromium.org

[erikchen, 2015-12-04 02:00:48]

tsepez: Please review.

[Tom Sepez, 2015-12-04 17:34:47]

lgtm

[erikchen, 2015-12-04 21:35:29]

The CQ bit was checked by erikchen@chromium.org

[commit-bot: I haz the power, 2015-12-04 21:36:39]

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

[commit-bot: I haz the power, 2015-12-04 21:48:33]

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

[commit-bot: I haz the power, 2015-12-04 21:48:34]

Try jobs failed on following builders:
  win8_chromium_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_ng/...)

[erikchen, 2015-12-05 00:03:24]

erikchen@chromium.org changed reviewers:
+ mark@chromium.org

[erikchen, 2015-12-05 00:03:25]

mark: Please review base/

[Mark Mentovai, 2015-12-05 00:14:15]

LGTM

[erikchen, 2015-12-08 01:18:58]

The CQ bit was checked by erikchen@chromium.org

[erikchen, 2015-12-08 01:18:58]

The patchset sent to the CQ was uploaded after l-g-t-m from tsepez@chromium.org,
mark@chromium.org
Link to the patchset: https://codereview.chromium.org/1493413004/#ps20001
(title: "gyp fix")

[commit-bot: I haz the power, 2015-12-08 01:19:50]

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

[commit-bot: I haz the power, 2015-12-08 04:04:52]

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

[commit-bot: I haz the power, 2015-12-08 04:04:54]

Try jobs failed on following builders:
  win8_chromium_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_ng/...)

[erikchen, 2015-12-31 01:39:07]

The CQ bit was checked by erikchen@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-12-31 01:39:12]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1493413004/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1493413004/20001

[commit-bot: I haz the power, 2015-12-31 01:46:51]

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

[commit-bot: I haz the power, 2015-12-31 01:46:52]

Dry run: Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[erikchen, 2016-01-04 21:09:06]

The CQ bit was checked by erikchen@chromium.org

[erikchen, 2016-01-04 21:09:06]

The patchset sent to the CQ was uploaded after l-g-t-m from tsepez@chromium.org,
mark@chromium.org
Link to the patchset: https://codereview.chromium.org/1493413004/#ps40001
(title: "Fix a double release bug.")

[commit-bot: I haz the power, 2016-01-04 21:10:40]

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

[commit-bot: I haz the power, 2016-01-04 22:20:47]

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

[commit-bot: I haz the power, 2016-01-04 22:20:48]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[erikchen, 2016-01-06 01:08:25]

Description was changed from

==========
ipc: Allow attachment brokering for shared memory handles.

Each shared memory handle is backed by a HANDLE, and that HANDLE is associated
with a specific process. If a shared memory handle passed to the Chrome IPC
stack is associated with the current process, the IPC stack will automatically
broker the handle to the destination process.

BUG=493414
==========

to

==========
ipc: Implement attachment brokering for SharedMemoryHandle on Windows.

Each SharedMemoryHandle is backed by a HANDLE, and that HANDLE is associated
with a specific process. If a SharedMemoryHandle passed to IPC is associated
with the current process, the IPC stack will automatically broker the handle to
the destination process.

This functionality has been implemented and tested, but is not yet turned on,
because there are a couple of Windows-specific Chrome IPC messages that
intentionally pass a HANDLE associated with another process. I will write a
follow-up CL that turns on this functionality, and removes those IPC messages.

BUG=493414
==========

[erikchen, 2016-01-06 01:08:41]

The CQ bit was checked by erikchen@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-01-06 01:09:23]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1493413004/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1493413004/80001

[erikchen, 2016-01-06 02:13:28]

The CQ bit was checked by erikchen@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-01-06 02:14:21]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1493413004/120001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1493413004/120001

[commit-bot: I haz the power, 2016-01-06 03:37:34]

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

[commit-bot: I haz the power, 2016-01-06 03:37:39]

Dry run: Try jobs failed on following builders:
  win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[erikchen, 2016-01-06 22:17:11]

The CQ bit was checked by erikchen@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-01-06 22:18:17]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1493413004/140001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1493413004/140001

[commit-bot: I haz the power, 2016-01-06 23:29:26]

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

[commit-bot: I haz the power, 2016-01-06 23:29:27]

Dry run: This issue passed the CQ dry run.

[erikchen, 2016-01-07 00:29:36]

tsepez: Please review again, as it's been a month and I've made some changes.

[Tom Sepez, 2016-01-07 23:02:41]

lgtm

[erikchen, 2016-01-08 00:52:34]

The CQ bit was checked by erikchen@chromium.org

[erikchen, 2016-01-08 00:52:35]

The patchset sent to the CQ was uploaded after l-g-t-m from mark@chromium.org
Link to the patchset: https://codereview.chromium.org/1493413004/#ps140001
(title: "Fix more tests.")

[commit-bot: I haz the power, 2016-01-08 00:53:20]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1493413004/140001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1493413004/140001

[commit-bot: I haz the power, 2016-01-08 02:17:12]

Committed patchset #8 (id:140001)

[commit-bot: I haz the power, 2016-01-08 02:18:42]

Description was changed from

==========
ipc: Implement attachment brokering for SharedMemoryHandle on Windows.

Each SharedMemoryHandle is backed by a HANDLE, and that HANDLE is associated
with a specific process. If a SharedMemoryHandle passed to IPC is associated
with the current process, the IPC stack will automatically broker the handle to
the destination process.

This functionality has been implemented and tested, but is not yet turned on,
because there are a couple of Windows-specific Chrome IPC messages that
intentionally pass a HANDLE associated with another process. I will write a
follow-up CL that turns on this functionality, and removes those IPC messages.

BUG=493414
==========

to

==========
ipc: Implement attachment brokering for SharedMemoryHandle on Windows.

Each SharedMemoryHandle is backed by a HANDLE, and that HANDLE is associated
with a specific process. If a SharedMemoryHandle passed to IPC is associated
with the current process, the IPC stack will automatically broker the handle to
the destination process.

This functionality has been implemented and tested, but is not yet turned on,
because there are a couple of Windows-specific Chrome IPC messages that
intentionally pass a HANDLE associated with another process. I will write a
follow-up CL that turns on this functionality, and removes those IPC messages.

BUG=493414

Committed: https://crrev.com/3d87ecf7392672dbd0aaabc042caf29cf63631cf
Cr-Commit-Position: refs/heads/master@{#368244}
==========

[commit-bot: I haz the power, 2016-01-08 02:18:43]

Patchset 8 (id:??) landed as
https://crrev.com/3d87ecf7392672dbd0aaabc042caf29cf63631cf
Cr-Commit-Position: refs/heads/master@{#368244}