summaryrefslogtreecommitdiffstats
path: root/lib/libc_r
Commit message (Collapse)AuthorAgeFilesLines
* Fix a race condition in pthread_join(). All of the following must occurjasone2001-06-273-48/+53
| | | | | | | | | | | | atomically: 1) Search _thread_list for the thread to join. 2) Search _dead_list for the thread to join. 3) Set the running thread as the joiner. While we're at it, fix a race in the case where multiple threads try to join on the same thread. POSIX says that the behavior of multiple joiners is undefined, but the fix is cheap as a result of the other fix.
* Typo fix: requires -> reacquiresgshapiro2001-06-271-1/+1
| | | | | Submitted by: Murray S. Kucherawy <msk@sendmail.com> MFC after: 3 days
* Add a missing word.dd2001-06-051-1/+1
| | | | Obtained from: OpenBSD
* Add a missing word.dd2001-06-051-1/+2
|
* Add a test for PR 24345.jasone2001-05-202-0/+110
|
* Update the verify script.jasone2001-05-202-201/+162
|
* Don't define _REENTRANT, since the Makefile does so.jasone2001-05-201-2/+0
|
* Fix a typo.jasone2001-05-201-1/+1
|
* Instead of using a join queue for each thread, use a single pointer tojasone2001-05-2011-146/+107
| | | | | | | | | | | keep track of a joiner. POSIX only supports a single joiner, so this simplification is acceptable. At the same time, make sure to mark a joined thread as detached so that its resources can be freed. Reviewed by: deischen PR: 24345
* Fixed typo in the description.ru2001-05-181-2/+2
| | | | | PR: docs/27411 Submitted by: David Wimsey <dwimsey@rtci.com>
* Condition variable waiters are queued in descending priority order, sojasone2001-05-181-9/+2
| | | | | | | | there is no need to wake all waiters to assure that the highest priority thread is run. As the semaphore code is written, there was no correctness problem, but the change improves sem_post() performance. Pointed out by: deischen
* Mark a thread that is suspended while sleeping as interrupted.jasone2001-05-161-1/+3
|
* Properly copy the P_ALTSTACK flag in struct proc::p_flag to the childknu2001-05-071-11/+1
| | | | | | | | | | | | | | | | | | process on fork(2). It is the supposed behavior stated in the manpage of sigaction(2), and Solaris, NetBSD and FreeBSD 3-STABLE correctly do so. The previous fix against libc_r/uthread/uthread_fork.c fixed the problem only for the programs linked with libc_r, so back it out and fix fork(2) itself to help those not linked with libc_r as well. PR: kern/26705 Submitted by: KUROSAWA Takahiro <fwkg7679@mb.infoweb.ne.jp> Tested by: knu, GOTOU Yuuzou <gotoyuzo@notwork.org>, and some other people Not objected by: hackers MFC in: 3 days
* Move the check for a pending signals to after the thread has beendeischen2001-05-042-6/+18
| | | | | | | | | | | | | | | placed in any scheduling queue(s). The process of dispatching signals to a thread can change its state which will attempt to add or remove the thread from any scheduling queue to which it belongs. This can break some assertions if the thread isn't in the queue(s) implied by its state. When adding dispatching a pending signal to a thread, be sure to remove the signal from the threads set of pending signals. PR: 27035 Tested by: brian MFC in: 1 week
* Compenate for header dethreading.markm2001-05-014-0/+8
|
* Typo; fix open() so that it is not a cancellation point when calleddeischen2001-04-181-1/+1
| | | | from libc.
* Reinstall the alternate signal stack after a fork.deischen2001-04-181-1/+11
| | | | | PR: 25110 Tested by: knu
* Clean up a bit. Use the correct TAILQ link when walking the threaddeischen2001-04-101-38/+71
| | | | | lists to free thread resources after a fork (in the child). Also remember to free the dead thread list.
* Added a missing set of braces to a conditional that encompasses more thandeischen2001-04-101-5/+6
| | | | one statement.
* To be consistent, use the __weak_reference macro from <sys/cdefs.h>deischen2001-04-10116-160/+160
| | | | | | instead of #pragma weak to create weak definitions. Suggested by: bde
* Activate build of posix1e extensions in libc and libc_r that have beentmm2001-04-041-0/+6
| | | | | | | | moved in from libposix1e, and deactivate build of the soon-to-be-removed libposix1e. Approved by: rwatson Obtained from: TrustedBSD Project
* Add thread safety wrappers for the posix1e syscalls that deal with filetmm2001-04-047-0/+294
| | | | | | | descriptors. Approved by: rwatson Obtained from: TrustedBSD Project
* Add a leading underscore to the pthread_main_np function name, andiedowse2001-04-031-1/+2
| | | | | | | | | a "#pragma weak" directive linking the external symbol. This matches the other pthread_* definitions, and ensures that users of this function from within libc get the real version, not the stub. Suggested by: deischen Reviewed by: deischen, alfred
* MAN[1-9] -> MAN.ru2001-03-271-1/+1
|
* Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) andalfred2001-03-192-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | associated changes that had to happen to make this possible as well as bugs fixed along the way. Bring in required TLI library routines to support this. Since we don't support TLI we've essentially copied what NetBSD has done, adding a thin layer to emulate direct the TLI calls into BSD socket calls. This is mostly from Sun's tirpc release that was made in 1994, however some fixes were backported from the 1999 release (supposedly only made available after this porting effort was underway). The submitter has agreed to continue on and bring us up to the 1999 release. Several key features are introduced with this update: Client calls are thread safe. (1999 code has server side thread safe) Updated, a more modern interface. Many userland updates were done to bring the code up to par with the recent RPC API. There is an update to the pthreads library, a function pthread_main_np() was added to emulate a function of Sun's threads library. While we're at it, bring in NetBSD's lockd, it's been far too long of a wait. New rpcbind(8) replaces portmap(8) (supporting communication over an authenticated Unix-domain socket, and by default only allowing set and unset requests over that channel). It's much more secure than the old portmapper. Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded to support TI-RPC and to support IPV6. Umount(8) is also fixed to unmount pathnames longer than 80 chars, which are currently truncated by the Kernel statfs structure. Submitted by: Martin Blapp <mb@imp.ch> Manpage review: ru Secure RPC implemented by: wpaul
* Correct a race condition where it was possible for a signaleddeischen2001-03-091-2/+8
| | | | | | | | thread to become stranded and not placed in the run queue. MFC Candidate Reported by: tegge
* mdoc(7) police: fix markup.ru2001-03-022-7/+9
|
* Use ``.St -p1003.1-96''.ru2001-02-2632-96/+64
|
* /^\.St/ s/-iso9945-1/-p1003.1-96/ru2001-02-266-6/+6
|
* Really set the flags for a private mutex (used by libc/libc_r).deischen2001-02-261-2/+5
|
* Limit threads clock resolution to no less than 1000usec (1000Hz).deischen2001-02-262-1/+3
| | | | | PR: 25300 Submitted by: Tom Pavel <pavel@alum.mit.edu> (in part)
* Remove (int) file descriptor locking. It should be up to thedeischen2001-02-115-478/+51
| | | | | | | | | | | | | application to provide locking for I/O operations. This doesn't break any of my tests, but the old behavior can be restored by compiling with _FDLOCKS_ENABLED. This will eventually be removed when it is obvious it does not cause any problems. Remove most of flockfile implementation, with the exception of flockfile_debug. Make error messages more informational (submitted by Mike Heffner <spock@techfour.net>, who's now known as mikeh@FreeBSD.org).
* Fix typo.nik2001-02-021-1/+1
| | | | | PR: docs/23936 Submitted by: Garret Rooney <rooneg@rpi.edu>
* mdoc(7) police: split punctuation characters + misc fixes.ru2001-02-012-2/+3
|
* s/_thread_sys_write/__sys_write/deischen2001-01-311-2/+2
| | | | Submitted by: Mike Heffner <mheffner@vt.edu>
* Unbreak world by correctly specifying the prototype for __sys_aio_suspend.deischen2001-01-291-1/+1
| | | | | | A make buildworld was done but not with the committed pthread_private.h. Reported by: Manfred Antar <null@pozo.com>
* _exit in libc is now __sys_exit not __sys__exit.deischen2001-01-293-7/+9
| | | | | | Add another check for thread library initialization (jdp, we really need a way to get _thread_init called at program start before any constructors are run).
* -pthread -> -lc_rdeischen2001-01-241-1/+1
|
* Add weak definitions for wrapped system calls. In general:deischen2001-01-24127-1350/+1464
| | | | | | | | | | | | | | | | | | | | | | | | | | | _foo - wrapped system call foo - weak definition to _foo and for cancellation points: _foo - wrapped system call __foo - enter cancellation point, call _foo(), leave cancellation point foo - weak definition to __foo Change use of global _thread_run to call a function to get the currently running thread. Make all pthread_foo functions weak definitions to _pthread_foo, where _pthread_foo is the implementation. This allows an application to provide its own pthread functions. Provide slightly different versions of pthread_mutex_lock and pthread_mutex_init so that we can tell the difference between a libc mutex and an application mutex. Threads holding mutexes internal to libc should never be allowed to exit, call signal handlers, or cancel. Approved by: -arch
* Force strong references to several pthread_* functions which are weaklyobrien2001-01-061-0/+32
| | | | | | | | | | | | | | | | referenced to by libgcc.a. This is needed when linking statically as SVR4 (ie, ELF) behavior is to only link in a module if it satisfies an undefined strong reference from somewhere. (this surprises a lot of people) Things are different when using shared libs, the entire library and its modules and their symbols are available at run-time (when the weak reference is seen to still be unsatisfied and is satisfied on the spot), this is not the case with static libs. Thus one can have a static binary with unresolved week references, and at run-time dereference a NULL pointer. Submitted by: eischen
* Use macro API to <sys/queue.h>phk2000-12-311-4/+4
| | | | | | | Submitted by: "Peter Avalos" <pavalos@theshell.com> Reviewed by: /sbin/md5 [*] [*] This line appears courtesy of Mr. Warner Losch, all rights reversed.
* Prepare for mdoc(7)NG.ru2000-12-291-0/+1
|
* When retrieving the time of day in nanosleep(), store it in thedeischen2000-12-201-4/+12
| | | | | | | | global time of day. This costs us nothing, but is a bit of a hack to work around a process blocking and not having the time updated by an ITIMER_PROF signal. PR: 23679
* Enable check for pending signals after calling a signal handler.deischen2000-12-201-0/+3
| | | | | | | Restoration of a threads signal mask after invocation of a signal handler may allow pending signals to become deliverable. PR: 23647
* mdoc(7) police: Er macro usage cleanup.ru2000-11-222-2/+6
|
* Change a "while {}" loop to a "do {} while" to allow it to bedeischen2000-11-202-3/+7
| | | | | | | | | | | | | executed at least once, fixing pthread_mutex_lock() for recursive mutex lock attempts. Correctly set a threads signal mask while it is executing a signal handler. The mask should be the union of its current mask, the signal being handled, and the mask from the signal action. Reported by: Dan Nelson <dnelson@emsphone.com> MFC Candidate
* Fix MD macros to work for alpha. Without this fix, threads under alphadeischen2000-11-201-4/+4
| | | | | | | | seem to be totally broke. MFC Candidate Submitted by: gallatin
* Fix a bug where a statically initialized condition variabledeischen2000-11-161-2/+2
| | | | | | | | | | was not getting properly initialized in pthread_cond_signal() and pthread_cond_broadcast(). Reportedly, this can cause an application to die. MFC candidate Submitted by: ade
* Delete 4 lines of misleading/incorrect comments.deischen2000-11-161-4/+0
|
* When entering the scheduler from the signal handler, telldeischen2000-11-144-19/+38
| | | | | | | | | | | the kernel to (re)use the alternate signal stack. In this case, we don't return normally from the signal handler, so the kernel still thinks we are using the signal stack. The fixes a nasty bug where the signal handler can start fiddling with the stack of a thread while the handler is actually running on the same stack. MFC candidate
OpenPOWER on IntegriCloud