A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=libressl-v2.2.4 2015-04-07T01:27:07+00:00 2015-04-07T01:27:07+00:00 guenther 2015-04-07T01:27:07+00:00 urn:sha1:fd187e2b735724c166cd750838f5169b96a51c6f unregistering callbacks if the DSO is unloaded. Move the callback handling from libpthread to libc, though libpthread still overrides the inner call to handle locking and thread-library reinitialization. Major version bump for both libc and libpthread. verification that this fixes various ports ajacoutot@ asm assistance miod@; ok millert@ deraadt@ 2011-10-16T06:29:56+00:00 guenther 2011-10-16T06:29:56+00:00 urn:sha1:a45814dbda3fe7b73d9575b576ba6477225985e6 handling to fix up the alignment of 64bit arguments so that they do the same dance where _thread_sys_FOO is the real stub and FOO is a weak alias. For some of them, this is needed for cancellation handling. From discussions with fgsch@, ok millert@ 2008-06-14T15:43:43+00:00 otto 2008-06-14T15:43:43+00:00 urn:sha1:5b5778393595ddb408f774ca0db7a9d40f6782f5 2008-06-13T21:18:42+00:00 otto 2008-06-13T21:18:42+00:00 urn:sha1:b65da525816f8a4366b3b8f09e0bbcec6ec867a6 2008-01-01T00:43:39+00:00 kurt 2008-01-01T00:43:39+00:00 urn:sha1:d08c4e4910d78ef0ddd9e7917c1f2d61b0021d4a instead of the generic pthread macros since free(3) uses __arc4_getbyte() when freeing small sized allocations and the generic pthread macros call malloc(3). - eliminate passing pointers to a static variable with global scope (rs) for additional code clarity and reduction. - shlib minor bumps for libc and libpthread due to new functions. From andreas@ with some bits from me. okay tedu@ marc@ w/some spot checking from millert@ 2007-11-19T02:54:19+00:00 kurt 2007-11-19T02:54:19+00:00 urn:sha1:82238b8a1552ad2206b7677e25095266b6f52a0f both static and non-static mutexs. 2007-06-05T18:11:48+00:00 kurt 2007-06-05T18:11:48+00:00 urn:sha1:a9f7df88bc0ab9f89af4f9e71a3e4daea3a14008 isolate its usage to libpthread only and replace with generic non-static mutex support in the one place it is needed: - remove _FD_LOCK/UNLOCK from lseek and ftruncate in libc and make the functions weak so that libpthread can override with its own new versions that do the locking. - remove _thread_fd_lock/unlock() weak functions from libc and adjust libpthread for the change. - add generic _thread_mutex_lock/unlock/destroy() weak functions in libc to support non-static mutexes in libc and add libpthread and librthread implementations for them. libc can utilize non-static mutexes via the new _MUTEX_LOCK/UNLOCK/DESTROY() macros. Actually these new macros can support both static and non-static mutexes but currently only using them for non-static. - make opendir/closedir/readdir/readdir_r/seekdir/telldir() thread-safe for both thread libraries by using a non-static mutex in the struct _dirdesc (typedef DIR), utilizing it in the *dir functions and remove remaining and incorrect _FD_LOCK/UNLOCK() use in libc. - add comments to both thread libraries to indicate libc depends on the current implementation of static mutex initialization. suggested by marc@ - major bump libc and libpthread due to function removal, structure change and weak symbol conversions. okay marc@, tedu@ 2006-09-26T14:18:28+00:00 kurt 2006-09-26T14:18:28+00:00 urn:sha1:3e7a96453995beff0dd6bfbefb9db0b02fbb7ef5 Adjust design of file descriptor table to eliminate races with both opening and closing of file descriptor entries and eliminates one class of deadlocks. One nice side effect of this change in design should be better performance for applications that open and close many file descriptors due to reduced fd_table_lock contention and fd entry reuse. - Add entry states to manage use of entry and eliminate some closing races. fd entries are not deallocated upon close() now. - Call _thread_fd_table_init with one of five discreet modes to properly initialize an entry and manage the state transition to open. - When closing an entry hold the entry spinlock locked across the state transition and the _thread_sys_close call to close another race. - Introduce a new lock type FD_RDWR_CLOSE that transitions either a closed entry or an open entry into closing state and then waits for a RDWR lock so that the lock queue can unwind normally. All subsequent fd lock attempts for that entry are rejected with EBADF until the fd is fully closed, or reopened by dup2(). Once a thread holds the FD_RDWR_LOCK it is safe to close() it or dup2() on it. - When a thread creates a new fd there is a window of time when another thread could attempt to use the fd before the creating thread has initialized the entry for it. This can result in improper status_flags for the entry, so record the entries init mode, detect when this has happened and correct the status_flags when needed. reviewed by marc@ & brad@, tested by several, okay brad@ 2006-02-22T07:16:32+00:00 otto 2006-02-22T07:16:32+00:00 urn:sha1:f79af607fea8db71524b8a4a1553fb437b284616 originally reported by Gergely Kovacs; help from dhartmei@; ok tedu@ millert@ 2005-11-15T11:56:40+00:00 millert 2005-11-15T11:56:40+00:00 urn:sha1:5aae9fa1f07b086b852d9795330efd3d419d8804 it has already been defined by previous includes. While this is true at the moment, it will no longer be true after a pending includes cleanup. OK marc@