FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F5.3.0 2004-10-30T00:08:46Z 2004-10-30T00:08:46Z Peter Wemm peter@FreeBSD.org 2004-10-30T00:08:46Z urn:sha1:ab74188ed68fcde054e5453479954765d3e8155e (I believe there will be a tag slide for this) Approved by: re (kensmith) 2004-10-16T08:43:07Z cvs2svn cvs2svn@FreeBSD.org 2004-10-16T08:43:07Z urn:sha1:5c5cd6c8e7b9cc9c39e56d04459ff9f4b2408bc1 2004-10-11T20:04:59Z Julian Elischer julian@FreeBSD.org 2004-10-11T20:04:59Z urn:sha1:38629e467ab9f357f2614aa6257feed03ec25799 Capture calls to execve() to make sure that the signal mask is set correctly on the thread that is going to continue in the new process. Required for Posix compliance. This is not perfect and better fixes may happen after 5.3 is released. Approved by: re (scottl) 2004-10-09T15:37:42Z Mike Makonnen mtm@FreeBSD.org 2004-10-09T15:37:42Z urn:sha1:199531033f3fc14fdcc09b2dfb319c01bf2bc571 revision 1.41 date: 2004/09/16 13:55:46; author: mtm; state: Exp; lines: +21 -0 Implement cancellation points in libc interfaces, as specified by POSIX. ============================================================================= Approved by: re/scottl 2004-10-09T15:13:50Z Mike Makonnen mtm@FreeBSD.org 2004-10-09T15:13:50Z urn:sha1:8bc61b56c6214408a374d76d5636e4b1d8329662 revision 1.32 date: 2004/09/22 18:51:16; author: mtm; state: Exp; lines: +1 -14 Remove vestiges of libthr's signal mangling past. This fixes that last known problem with mysql on libthr: not being able to kill mysqld. ---------------------------- revision 1.31 date: 2004/09/22 16:53:23; author: mtm; state: Exp; lines: +6 -27 The SUSv3 function say that the affected functions MAY FAIL, if the specified mutex is invalid. In spec parlance 'MAY FAIL' means it's up to the implementor. So, remove the check for NULL pointers for two reasons: 1. A mutex may be invalid without necessarily being NULL. 2. If the pointer to the mutex is NULL core-dumping in the vicinity of the problem is much much much better than failing in some other part of the code (especially when the application doesn't check the return value of the function that you oh so helpfully set to EINVAL). ============================================================================= Approved by: re/scottl 2004-10-09T15:12:33Z Mike Makonnen mtm@FreeBSD.org 2004-10-09T15:12:33Z urn:sha1:101596b827d3570cefefd0b8a26a0e2e5cb7c23f ---------------------------- revision 1.15 date: 2004/10/08 14:48:02; author: mtm; state: Exp; lines: +1 -4 Remove a reference to a non-existent syscall: _thr_exit(). The actual name is thr_exit(). How this ever worked is beyond me. ---------------------------- revision 1.14 date: 2004/10/06 14:20:57; author: mtm; state: Exp; lines: +2 -3 Close a race between a thread exiting and the freeing of it's stack. After some discussion the best option seems to be to signal the thread's death from within the kernel. This requires that thr_exit() take an argument. Discussed with: davidxu, deischen, marcel MFC after: 3 days ============================================================================= Approved by: re/scottl 2004-10-09T15:07:20Z Mike Makonnen mtm@FreeBSD.org 2004-10-09T15:07:20Z urn:sha1:8cf0e32cc809d7171cddc38ae0387451bce661af lib/Makefile: ---------------------------- revision 1.1 date: 2004/08/19 23:41:12; author: davidxu; state: Exp; Add AMD64 support code. ============================================================================= RCS file: /home/ncvs/src/lib/libthr/arch/i386/i386/_setcurthread.c,v ---------------------------- revision 1.15 date: 2004/08/19 23:49:04; author: davidxu; state: Exp; lines: +10 -3 Adjust code to support AMD64, on AMD64, thread needs to set fsbase by itself before it can execute any other code, so new thread should be created with all signals are masked until after fsbase is set. ============================================================================= RCS file: /home/ncvs/src/lib/Makefile,v ---------------------------- revision 1.190 date: 2004/08/19 23:51:42; author: davidxu; state: Exp; lines: +1 -2 build libthr on amd64. ============================================================================= Approved by: re/scottl 2004-10-09T10:21:19Z David Xu davidxu@FreeBSD.org 2004-10-09T10:21:19Z urn:sha1:e55314ae0809b1f420ec539d6660e15fe99f2f32 Allocate red zone and stack space together and then split red zone from allocated space, orignal code left red zone unallocated, but those space can be allocated by user code, and result was providing no protection. Approved by: re (scottl) 2004-10-09T07:31:04Z cvs2svn cvs2svn@FreeBSD.org 2004-10-09T07:31:04Z urn:sha1:e6cea8cec4ef932dbdded00cd22756e7f57d5110 2004-10-02T02:01:51Z Scott Long scottl@FreeBSD.org 2004-10-02T02:01:51Z urn:sha1:767028da93c338cdd7ae5326023f6ea17efc35c2 libc, libc_r, and libperl. Approved by: re