Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | overhaul pthread cancellation | Rich Felker | 2011-04-17 | 1 | -0/+36 |
| | | | | | | | | | | | | | | | | | | | | | | this patch improves the correctness, simplicity, and size of cancellation-related code. modulo any small errors, it should now be completely conformant, safe, and resource-leak free. the notion of entering and exiting cancellation-point context has been completely eliminated and replaced with alternative syscall assembly code for cancellable syscalls. the assembly is responsible for setting up execution context information (stack pointer and address of the syscall instruction) which the cancellation signal handler can use to determine whether the interrupted code was in a cancellable state. these changes eliminate race conditions in the previous generation of cancellation handling code (whereby a cancellation request received just prior to the syscall would not be processed, leaving the syscall to block, potentially indefinitely), and remedy an issue where non-cancellable syscalls made from signal handlers became cancellable if the signal handler interrupted a cancellation point. x86_64 asm is untested and may need a second try to get it right. | ||||
* | match glibc/lsb cancellation abi on i386 | Rich Felker | 2011-03-25 | 2 | -0/+24 |
| | | | | | | | | glibc made the ridiculous choice to use pass-by-register calling convention for these functions, which is impossible to duplicate directly on non-gcc compilers. instead, we use ugly asm to wrap and convert the calling convention. presumably this works with every compiler anyone could potentially want to use. | ||||
* | race condition fix: block all signals before decrementing thread count | Rich Felker | 2011-02-19 | 1 | -9/+0 |
| | | | | | | | | | | | | the existence of a (kernelspace) thread must never have observable effects after the thread count is decremented. if signals are not blocked, it could end up handling the signal for rsyscall and contributing towards the count of threads which have changed ids, causing a thread to be missed. this could lead to one thread retaining unwanted privilege level. this change may also address other subtle race conditions in application code that uses signals. | ||||
* | finish unifying thread register handling in preparation for porting | Rich Felker | 2011-02-15 | 1 | -0/+22 |
| | |||||
* | begin unifying clone/thread management interface in preparation for porting | Rich Felker | 2011-02-15 | 1 | -25/+17 |
| | |||||
* | initial check-in, version 0.5.0 v0.5.0 | Rich Felker | 2011-02-12 | 2 | -0/+57 |