summaryrefslogtreecommitdiffstats
path: root/lib/libpthread
Commit message (Collapse)AuthorAgeFilesLines
...
* For errors, return -1 and set errno to indicate the error type, rather thanjasone2000-02-161-16/+33
| | | | | | | | | returning the error directly. For sem_post(), make sure that the correct thread is woken up. This has unfortunate performance implications, but is necessary for POSIX compliance. Approved by: jkh
* Add man pages for the sem_*() functions.jasone2000-02-167-4/+516
| | | | Approved by: jkh
* Use __strong_reference() instead of __weak_reference() to assure that thejasone2000-01-2911-11/+11
| | | | weak symbols of the same name are not used.
* Use _fcntl() (not fcntl()) inside of fcntl().jasone2000-01-281-3/+3
| | | | Reported by: green
* Simplify sytem call renaming. Instead of _foo() <-- _libc_foo <-- foo(),jasone2000-01-2733-81/+571
| | | | | | | | | | | | | | | | | just use _foo() <-- foo(). In the case of a libpthread that doesn't do call conversion (such as linuxthreads and our upcoming libpthread), this is adequate. In the case of libc_r, we still need three names, which are now _thread_sys_foo() <-- _foo() <-- foo(). Convert all internal libc usage of: aio_suspend(), close(), fsync(), msync(), nanosleep(), open(), fcntl(), read(), and write() to _foo() instead of foo(). Remove all internal libc usage of: creat(), pause(), sleep(), system(), tcdrain(), wait(), and waitpid(). Make thread cancellation fully POSIX-compliant. Suggested by: deischen
* Fix millisecond to nanosecond conversion.jasone2000-01-221-1/+1
| | | | PR: misc/16245
* Minor *jmp() cleanups.jasone2000-01-201-2/+3
|
* Add sem_*() functions. Named semaphores and process-shared semaphoresjasone2000-01-203-0/+237
| | | | | | | are not supported by this implementation, and the error return values from sem_init(), sem_open(), sem_close(), and sem_unlink() reflect this. Approved by: jkh
* Do signal deferral for pthread_kill() as it was done in the old days.jasone2000-01-203-30/+6
| | | | Submitted by: deischen
* Implement continuations to correctly handle [sig|_]longjmp() inside of ajasone2000-01-1912-61/+374
| | | | | | | | | | | | | | | | | | | | | | signal handler. Explicitly check for jumps to anywhere other than the current stack, since such jumps are undefined according to POSIX. While we're at it, convert thread cancellation to use continuations, since it's cleaner than the original cancellation code. Avoid delivering a signal to a thread twice. This was a pre-existing bug, but was likely unexposed until these other changes were made. Defer signals generated by pthread_kill() so that they can be delivered on the appropriate stack. deischen claims that this is unnecessary, which is likely true, but without this change, pthread_kill() can cause undefined priority queue states and/or PANICs in [sig|_]longjmp(), so I'm leaving this in for now. To compile this code out and exercise the bug, define the _NO_UNDISPATCH cpp macro. Defining _PTHREADS_INVARIANTS as well will cause earlier crashes. PR: kern/14685 Collaboration with: deischen
* Properly initialize the last active time of the initial thread. This fixesdeischen2000-01-181-0/+6
| | | | | | | the case that a CPU hungry main thread is prevented from being preempted due to a negative calculation of its time slice. Reported by: Alexander Litvin <archer@lucky.net>
* Track libc's three-tier symbol naming. libc_r must currently implementjasone2000-01-1226-32/+75
| | | | | the _libc_*() entry points and add *() weak aliases. This will all change for the better when libc_r becomes libpthread.
* Make sched_param parameter a const to comply with POSIX and SUSv2 specs.deischen2000-01-101-1/+1
| | | | | | | This doesn't need to be applied to stable, because somehow -stable seems to have gotten it right. Reviewed by: jasone
* Don't explicitly mmap() red zones at the bottom of thread stacks (exceptjasone1999-12-293-16/+26
| | | | | | | | | | the initial thread). Instead, just leave an unmapped gap between thread stacks and make sure that the thread stacks won't grow into these gaps, simply by limiting the size of the stacks with the 'len' argument to mmap(). This (if I understand correctly) reduces VM overhead considerably. Reviewed by: deischen
* -Wall and minor style(9) cleanups.deischen1999-12-287-16/+14
|
* Change stack allocation algorithm to make better use of memorydeischen1999-12-282-22/+20
| | | | | (it was leaving an unused block). Also protect the global stack pointer from context changes while fiddling with it.
* Don't wakeup threads when there is a process signal and no installeddeischen1999-12-281-23/+37
| | | | | | | | handler. Thread-to-thread signals (pthread_signal) are treated differently than process signals; a pthread_signal can wakeup a blocked thread if a signal handler is not installed for that signal. Found by: ACE tests
* Fixed bitrot in synopsis. The change from "int *pshared" to "int pshared"bde1999-12-231-1/+1
| | | | hadn't reached here.
* Fix some minor POSIX/SUSv2 compliance nits.jasone1999-12-182-7/+5
| | | | PR: kern/11982
* Fix typosphantom1999-12-174-5/+8
| | | | | PR: docs/14858 Submitted by: OKAZAKI Tetsurou <okazaki@be.to>
* Fix problems with cancellation while in critical regions.deischen1999-12-176-8/+21
| | | | | | | | | | | o Cancellation flags were not getting properly set/cleared. o Loops waiting for internal locks were not being exited correctly by a cancelled thread. o Minor spelling (cancelation -> cancellation) and formatting corrections (missing tab). Found by: tg Reviewed by: jasone
* Fixes for signal handling:deischen1999-12-175-147/+208
| | | | | | | | | | | | | | o Don't call signal handlers with the signal handler access lock held. o Remove pending signals before calling signal handlers. If pending signals were not removed prior to handling them, invocation of the handler could cause the handler to be called more than once for the same signal. Found by: JB o When SIGCHLD arrives, wake up all threads in PS_WAIT_WAIT (wait4). PR: bin/15328 Reviewed by: jasone
* Avoid an infinite loop if the last element of the iov array passed tojasone1999-12-161-1/+13
| | | | | | writev() has an iov_len of 0. PR: bin/8281
* Change signal handling to conform to POSIX specified semantics.deischen1999-12-044-27/+79
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before this change, a signal was delivered to each thread that didn't have the signal masked. Signals also improperly woke up threads waiting on I/O. With this change, signals are now handled in the following way: o If a thread is waiting in a sigwait for the signal, then the thread is woken up. o If no threads are sigwait'ing on the signal and a thread is in a sigsuspend waiting for the signal, then the thread is woken up. o In the case that no threads are waiting or suspended on the signal, then the signal is delivered to the first thread we find that has the signal unmasked. o If no threads are waiting or suspended on the signal, and no threads have the signal unmasked, then the signal is added to the process wide pending signal set. The signal will be delivered to the first thread that unmasks the signal. If there is an installed signal handler, it is only invoked if the chosen thread was not in a sigwait. In the case that multiple threads are waiting or suspended on a signal, or multiple threads have the signal unmasked, we wake up/deliver the signal to the first thread we find. The above rules still apply. Reported by: Scott Hess <scott@avantgo.com> Reviewed by: jb, jasone
* * Fix the stack allocation code so that it works for alpha. Change itdfr1999-11-282-6/+26
| | | | | | | | | to use mmap(..., MAP_STACK, ...) on alpha too since that should work now. * Add hooks to allow GDB to access the internals of pthreads without having to know the exact layout of struct pthread. Reviewed by: deischen
* add pthread_cancel, obtained from OpenBSD.alfred1999-11-2830-73/+771
| | | | | | | | | | | | | | eischen (Daniel Eischen) added wrappers to protect against cancled threads orphaning internal resources. the cancelability code is still a bit fuzzy but works for test programs of my own, OpenBSD's and some examples from ORA's books. add readdir_r to both libc and libc_r add some 'const' attributes to function parameters Reviewed by: eischen, jasone
* Add sigsuspend.o and sigpending.o to HIDDEN_SYSCALLS as well.marcel1999-10-141-2/+2
| | | | Pointed out by: jdp
* Add sigprocmask to HIDDEN_SYSCALLS. This renames the syscall tomarcel1999-09-301-1/+2
| | | | | | _thread_sys_sisprocmask in libc_r. This solves the undefined symbol... Reported by: Kenneth Wayne Culver
* Add the proper headers so that the SIGNOTEMPTY and SIGSETANDmarcel1999-09-301-0/+2
| | | | macros are defined.
* sigset_t change (part 5 of 5)marcel1999-09-298-17/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ----------------------------- Most of the userland changes are in libc. For both the alpha and the i386 setjmp has been changed to accomodate for the new sigset_t. Internally, libc is mostly rewritten to use the new syscalls. The exception is in compat-43/sigcompat.c The POSIX thread library has also been rewritten to use the new sigset_t. Except, that it currently only handles NSIG signals instead of the maximum _SIG_MAXSIG. This should not be a problem because current applications don't use any signals higher than NSIG. There are version bumps for the following libraries: libdialog libreadline libc libc_r libedit libftpio libss These libraries either a) have one of the modified structures visible in the interface, or b) use sigset_t internally and may cause breakage if new binaries are used against libraries that don't have the sigset_t change. This not an immediate issue, but will be as soon as applications start using the new range to its fullest. NOTE: libncurses already had an version bump and has not been given one now. NOTE: doscmd is a real casualty and has been disconnected for the moment. Reconnection will eventually happen after doscmd has been fixed. I'm aware that being the last one to touch it, I'm automaticly promoted to being maintainer. According to good taste this means that I will receive a badge which either will be glued or mechanically stapled, drilled or otherwise violently forced onto me :-) NOTE: pcvt/vttest cannot be compiled with -traditional. The change cause sys/types to be included along the way which contains the const and volatile modifiers. I don't consider this a solution, but more a workaround.
* Fix a memory leak: free the thread-specific poll_data, used in the select()dt1999-08-301-0/+6
| | | | | | | implementation. PR: 13368 Submitted by: Steve Bernacki, Jr. <steve@copacetic.net>
* When checking for valid timevals in the wrapped select() and poll()deischen1999-08-303-9/+14
| | | | | routines, don't return EINVAL but set errno to EINVAL and return -1. Added a check in pthread_cond_timedwait for a null timespec pointer.
* $Id$ -> $FreeBSD$peter1999-08-28118-119/+119
|
* move sanity check of timeval struct so as not to segfault when passedalfred1999-08-201-5/+5
| | | | | | | a null pointer. Pointed out by: Thomas Gellekum <tg@ihf.rwth-aachen.de> Reviewed by: eivind
* When checking if there is a stack to free, observe the fact that itjb1999-08-201-6/+23
| | | | | | | | might have been mmapped, and if so, passing the pointer to free() is really not a good idea. [ In the next millenium, when I've taken over the world, I'm going to ban 8 character tabs. You've been warned. ]
* Fix EINVAL related descriptions.rse1999-08-202-6/+7
|
* time_to_sleep->tv_nsec > 1000000000alfred1999-08-191-2/+2
| | | | | -to- time_to_sleep->tv_nsec >= 1000000000
* Sanity check time structures passed in, return EINVAL like the systemalfred1999-08-194-6/+18
| | | | | | | | calls do to avoid corrupting the thread library's concept of wakeup time. PR: kern/12141 Reviewed by: deischen, eivind
* handle under/overflow of time values in a more robust manner,alfred1999-08-191-3/+3
| | | | | | | | there may be an overflow that need to be adjusted more than once. Pointed out by: Fabian Thylmann <fthylmann@stats.net> Reviewed by: eivind, jb
* Bad reference exit(2) changed to exit(3)chris1999-08-141-2/+2
|
* Add check for runnable threads before polling file descriptors.deischen1999-08-121-14/+16
| | | | Submitted by: tegge
* Add RCS IDs to those files without them.deischen1999-08-0568-74/+120
| | | | | | | Fix copyrights (s/REGENTS/AUTHOR). Suggested by: tg Approved by: jb
* Fix thread initialization to allow for the case where stdio filedeischen1999-08-052-11/+15
| | | | | | | descriptors are not opened. PR: bin/12853 Reviewed by: jb
* Add $Id$, to make it simpler for members of the translation teams tonik1999-07-1223-0/+46
| | | | | | | | | | | | | | | | | track. The $Id$ line is normally at the bottom of the main comment block in the man page, separated from the rest of the manpage by an empty comment, like so; .\" $Id$ .\" If the immediately preceding comment is a @(#) format ID marker than the the $Id$ will line up underneath it with no intervening blank lines. Otherwise, an additional blank line is inserted. Approved by: bde
* Use USRSTACK (defined in <machine/vmparam.h>) to get top of the initial stack.dt1999-07-122-16/+6
| | | | PTHREAD_STACK_TOP was wrong for all supported architectures.
* Fix a couple more coding style nits.jasone1999-07-112-5/+5
|
* Modify previous changes to conform better to libc_r's coding style.jasone1999-07-114-76/+113
| | | | | | | | Always use mmap() for default-size stack allocation. Use MAP_ANON instead of MAP_STACK on the alpha architecture. Reduce the amount of code executed while owning _gc_mutex during stack allocation.
* Always use growable thread stacks on the i386. The VM_STACK kernel optionjasone1999-07-065-31/+18
| | | | | must be made default for the alpha before growable thread stacks are enabled for the alpha.
* Disable growable stacks by default, as advertised.jasone1999-07-051-2/+2
|
* Use growable stacks for thread stacks that are the default stack size.jasone1999-07-055-22/+164
| | | | | | | | | | | | | Cache discarded default thread stacks for use in subsequent thread creations. Create a red zone at the end of each stack (including the initial thread stack), with the hope of causing a segfault if a stack overflows. To activate these modifications, add -D_PTHREAD_GSTACK to CFLAGS in src/lib/libc_r/Makefile. Since the modifications depend on the VM_STACK kernel option, I'm not sure how to safely use growable stacks by default. Testing, as well as algorithmic and stylistic comments are welcome.
OpenPOWER on IntegriCloud