tree 18ad351a86cabf94c2bb7f4f8b9dff9d0ec7c59a
parent da2d78ba97d177b80e0e9528362bcebc1fd31f0f
author Daniel Colascione <dancol@google.com> 1479767742 -0800
committer Daniel Colascione <dancol@google.com> 1479771846 -0800

Correctly handle EINTR return from futex

We should handle EINTR the same way we do EAGAIN: they're both
transient failures. Either way, higher-level code (see
ReaderWriterMutex::SharedLock) will do the right thing, loop around,
and try again.

Test: code inspection
Change-Id: I1eb7fb6851cc1a65acc9a0cf7cbeef787b6b28b6