[mojo-edk] Reset Port::send_on_proxy_removal after sending message.

[mojo-edk] Reset Port::send_on_proxy_removal after sending message.

If two threads try to call Node::MaybeRemoveProxy_Locked and both end up
trying to send the proxy removal message, the second attempt will result
in a null message since the first one moved it into ForwardMessage.

BUG=619522
Committed: https://crrev.com/2bb5f5da90bf2584f7f971fed962ce6a564bc3be
Cr-Commit-Position: refs/heads/master@{#399664}

[Anand Mistry (off Chromium), 2016-06-14 05:04:19]

amistry@chromium.org changed reviewers:
+ rockot@chromium.org

[Ken Rockot(use gerrit already), 2016-06-14 05:06:59]

lgtm

[Anand Mistry (off Chromium), 2016-06-14 05:08:06]

Description was changed from

==========
[mojo-edk] Reset Port::send_on_proxy_removal after sending message.

If two threads try to call Node::MaybeRemoveProxy_Locked and both end up
trying to send the proxy removal message, the send attempt will result
in a null message since the first one moved it into ForwardMessage.

BUG=619522
==========

to

==========
[mojo-edk] Reset Port::send_on_proxy_removal after sending message.

If two threads try to call Node::MaybeRemoveProxy_Locked and both end up
trying to send the proxy removal message, the second attempt will result
in a null message since the first one moved it into ForwardMessage.

BUG=619522
==========

[Anand Mistry (off Chromium), 2016-06-14 05:08:29]

The CQ bit was checked by amistry@chromium.org

[commit-bot: I haz the power, 2016-06-14 05:08:46]

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

[commit-bot: I haz the power, 2016-06-14 06:36:17]

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

[commit-bot: I haz the power, 2016-06-14 06:36:18]

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

[Anand Mistry (off Chromium), 2016-06-14 06:42:50]

The CQ bit was checked by amistry@chromium.org

[commit-bot: I haz the power, 2016-06-14 06:43:00]

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

[commit-bot: I haz the power, 2016-06-14 07:24:12]

Description was changed from

==========
[mojo-edk] Reset Port::send_on_proxy_removal after sending message.

If two threads try to call Node::MaybeRemoveProxy_Locked and both end up
trying to send the proxy removal message, the second attempt will result
in a null message since the first one moved it into ForwardMessage.

BUG=619522
==========

to

==========
[mojo-edk] Reset Port::send_on_proxy_removal after sending message.

If two threads try to call Node::MaybeRemoveProxy_Locked and both end up
trying to send the proxy removal message, the second attempt will result
in a null message since the first one moved it into ForwardMessage.

BUG=619522
==========

[commit-bot: I haz the power, 2016-06-14 07:24:13]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-14 07:24:15]

CQ bit was unchecked

[commit-bot: I haz the power, 2016-06-14 07:27:23]

Description was changed from

==========
[mojo-edk] Reset Port::send_on_proxy_removal after sending message.

If two threads try to call Node::MaybeRemoveProxy_Locked and both end up
trying to send the proxy removal message, the second attempt will result
in a null message since the first one moved it into ForwardMessage.

BUG=619522
==========

to

==========
[mojo-edk] Reset Port::send_on_proxy_removal after sending message.

If two threads try to call Node::MaybeRemoveProxy_Locked and both end up
trying to send the proxy removal message, the second attempt will result
in a null message since the first one moved it into ForwardMessage.

BUG=619522

Committed: https://crrev.com/2bb5f5da90bf2584f7f971fed962ce6a564bc3be
Cr-Commit-Position: refs/heads/master@{#399664}
==========

[commit-bot: I haz the power, 2016-06-14 07:27:24]

Patchset 1 (id:??) landed as
https://crrev.com/2bb5f5da90bf2584f7f971fed962ce6a564bc3be
Cr-Commit-Position: refs/heads/master@{#399664}