| commit | 6f4d102e0c3029b3c74af13d3846a14e1c878a12 | [log] [tgz] |
|---|---|---|
| author | Daniel Colascione <dancol@google.com> | Mon Nov 21 14:35:42 2016 -0800 |
| committer | Daniel Colascione <dancol@google.com> | Mon Nov 21 15:44:06 2016 -0800 |
| tree | 18ad351a86cabf94c2bb7f4f8b9dff9d0ec7c59a | |
| parent | da2d78ba97d177b80e0e9528362bcebc1fd31f0f [diff] |
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