3391a9ff13
This doesn't affect code like Chrome that correctly ignores EINTR on close, makes code that tries TEMP_FAILURE_RETRY work (where before it might have closed a different fd and appeared to succeed, or had a bogus EBADF), and makes "goto fail" code work (instead of mistakenly assuming that EINTR means that the close failed). Who loses? Anyone actively trying to detect that they caught a signal while in close(2). I don't think those people exist, and I think they have better alternatives available. Bug: https://code.google.com/p/chromium/issues/detail?id=269623 Bug: http://b/20501816 Change-Id: I11e2f66532fe5d1b0082b2433212e24bdda8219b
22 lines
434 B
ArmAsm
22 lines
434 B
ArmAsm
/* Generated by gensyscalls.py. Do not edit. */
|
|
|
|
#include <private/bionic_asm.h>
|
|
|
|
ENTRY(___close)
|
|
pushl %ebx
|
|
.cfi_def_cfa_offset 8
|
|
.cfi_rel_offset ebx, 0
|
|
mov 8(%esp), %ebx
|
|
movl $__NR_close, %eax
|
|
int $0x80
|
|
cmpl $-MAX_ERRNO, %eax
|
|
jb 1f
|
|
negl %eax
|
|
pushl %eax
|
|
call __set_errno_internal
|
|
addl $4, %esp
|
|
1:
|
|
popl %ebx
|
|
ret
|
|
END(___close)
|
|
.hidden ___close
|