Don't call the other wait set impl dispatcher methods under mutex either.

Don't call the other wait set impl dispatcher methods under mutex either.

Previously, I only did this for WaitSetWaitImpl(). But then I realized
that WaitSetAddImpl() and WaitSetRemoveImpl() also need to deal with the
mutex carefully (i.e., not do everything under the mutex) since I need
to avoid calling other dispatchers' AddAwakable()/RemoveAwakable() under
the mutex.

R=vardhan@google.com
BUG=#350

Committed: https://chromium.googlesource.com/external/mojo/+/1f06dce1f391be3e823d598a502ae7d047ec6ff7

[vardhan, 2016-06-14 17:03:47]

lgtm

[viettrungluu, 2016-06-14 17:21:10]

Description was changed from

==========
Don't call the other wait set impl dispatcher methods under mutex either.

Previously, I only did this for WaitSetWaitImpl(). But then I realized
that WaitSetAddImpl() and WaitSetRemoveImpl() also need to deal with the
mutex carefully (i.e., not do everything under the mutex) since I need
to avoid calling other dispatchers' AddAwakable()/RemoveAwakable() under
the mutex.

R=vardhan@google.com
BUG=#350
==========

to

==========
Don't call the other wait set impl dispatcher methods under mutex either.

Previously, I only did this for WaitSetWaitImpl(). But then I realized
that WaitSetAddImpl() and WaitSetRemoveImpl() also need to deal with the
mutex carefully (i.e., not do everything under the mutex) since I need
to avoid calling other dispatchers' AddAwakable()/RemoveAwakable() under
the mutex.

R=vardhan@google.com
BUG=#350

Committed:
https://chromium.googlesource.com/external/mojo/+/1f06dce1f391be3e823d598a502...
==========

[viettrungluu, 2016-06-14 17:21:12]

Committed patchset #1 (id:1) manually as
1f06dce1f391be3e823d598a502ae7d047ec6ff7 (presubmit successful).