wireguard-openbsd/lib/libpthread/man, branch master WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/lib/libpthread/man?h=master 2020-12-03T07:05:03Z There are special rules regarding the memory passed to pthread_attr_setstack(). 2020-12-03T07:05:03Z otto otto@openbsd.org 2020-12-03T07:05:03Z urn:sha1:0abccc37ae616c654d8c1a75cd149f63652b4ba0 ok semarie@ Update my email address. 2020-04-06T00:01:08Z pirofti pirofti@openbsd.org 2020-04-06T00:01:08Z urn:sha1:8855e28c066fcedf8b2ce6df476d3f9b3d0ee8f9 Clarify conditions in which pthread_mutex_destroy(3) returns EBUSY. 2020-04-03T13:05:08Z stsp stsp@openbsd.org 2020-04-03T13:05:08Z urn:sha1:25b7f502516e2f1c6e01335bfd66c89e94faf9c4 It happens not just if the mutex is locked by another thread, but also if any other threads refer to the mutex (e.g. by waiting for the lock). ok guenther Remove IMPLEMENTATION NOTES, they only apply to one of the two in-tree 2019-02-13T23:54:10Z mpi mpi@openbsd.org 2019-02-13T23:54:10Z urn:sha1:3229ec54b30580d61ef9c5943bf31a024ccfa29d implementations. Pointed out by pirofti@ tweak previous; 2019-02-04T18:06:32Z jmc jmc@openbsd.org 2019-02-04T18:06:32Z urn:sha1:cbc203c2342cad25c36cab2a7f220b3873c2ba6c add a pthread_get_name_np to match pthread_set_name_np. 2019-02-04T17:18:08Z tedu tedu@openbsd.org 2019-02-04T17:18:08Z urn:sha1:295117693e3a1d8af9cc3004578ce352f938d83a could be useful in ports. initial diff by David Carlier some time ago. ok jca Tweak description, pthread_cond_signal(3) unblocks *at least* one thread. 2019-01-29T17:38:48Z mpi mpi@openbsd.org 2019-01-29T17:38:48Z urn:sha1:826955895b7686c592de2e90525c30542d3cd1c2 ok kettenis@, visa@ Move sigwait(3) from libpthread to libc 2019-01-12T00:16:03Z jca jca@openbsd.org 2019-01-12T00:16:03Z urn:sha1:13e54a3ce65615faaf13e4717a510eb52bfb2efe POSIX wants it in libc, that's where the function can be found on other systems. Reported by naddy@, input from naddy@ and guenther@. "looks ok" guenther@, ok deraadt@ Note: riding the libc/libpthread major cranks earlier today. Validate timespec and return ECANCELED when interrupted with SA_RESTART. 2018-04-24T16:28:42Z pirofti pirofti@openbsd.org 2018-04-24T16:28:42Z urn:sha1:bda456ccd11759e253796707fd980cfc75ecc76d Discussing with mpi@ and guenther@, we decided to first fix the existing semaphore implementation with regards to SA_RESTART and POSIX compliant returns in the case where we deal with restartable signals. Currently we return EINTR everywhere which is mostly incorrect as the user can not know if she needs to recall the syscall or not. Return ECANCELED to signal that SA_RESTART was set and EINTR otherwise. Regression tests pass and so does the posixsuite. Timespec validation bits are needed to pass the later. OK mpi@, guenther@ Implement MAP_STACK option for mmap(). Synchronous faults (pagefault and 2018-04-12T17:13:34Z deraadt deraadt@openbsd.org 2018-04-12T17:13:34Z urn:sha1:003f5e42bbc90263e30dbce6eb150fc5e31b56eb syscall) confirm the stack register points at MAP_STACK memory, otherwise SIGSEGV is delivered. sigaltstack() and pthread_attr_setstack() are modified to create a MAP_STACK sub-region which satisfies alignment requirements. Observe that MAP_STACK can only be set/cleared by mmap(), which zeroes the contents of the region -- there is no mprotect() equivalent operation, so there is no MAP_STACK-adding gadget. This opportunistic software-emulation of a stack protection bit makes stack-pivot operations during ROPchain fragile (kind of like removing a tool from the toolbox). original discussion with tedu, uvm work by stefan, testing by mortimer ok kettenis