diff options
| author | Shubham Ajmera <shubhamajmera@google.com> | 2016-09-26 16:27:57 +0100 |
|---|---|---|
| committer | Shubham Ajmera <shubhamajmera@google.com> | 2016-10-26 10:47:23 +0000 |
| commit | d61baf5989fd43e2ca8fcbf98684264334541470 (patch) | |
| tree | 8015ba96f47d3c7f0250555da029ecb992cca183 /annotations/generate_annotated_java_files.py | |
| parent | b2d6966995331f09a87ae774d894f4ea4d1e0bfc (diff) | |
Revert commit eeb3b74d18cc9066ec3068a06d95d314c464ea5f
The CL introduces back the pre-close mechanism for Sockets. When a
thread calls close on a socket, it pre-closes the fd, i.e. dup2-ed the
file descriptor to a marker_fd. Marker_fd is a AF_UNIX file descriptor
with both read and write disable. Now, other threads which have already
acquired the file descriptor tries to read/write to it get EOF/error
correspondingly. When all the threads finally stop using the file
descriptor i.e. releases file descriptor, fd finally gets closed.
Without the pre-close, there are chances that other threads which are
about to write to the file descriptor after the close might end up
writing to the wrong file descriptor as they recycle quickly.
Test: Introduced several new test failures. Will be fixed in follow up CLs.
Bug: 27376593
Change-Id: I81eddecdab3df59c9639da27ec242b311ef575e0
Diffstat (limited to 'annotations/generate_annotated_java_files.py')
0 files changed, 0 insertions, 0 deletions