| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
the link arguments.
|
|
|
|
|
|
|
|
|
|
|
| |
used LIBTHREAD_1_0 as its version definition, but now needs
to define its symbols in the same namespace used by libc.
The compatibility hooks allows you to use libraries and
binaries built and linked to libpthread before libc was
built with symbol versioning. The shims can be removed if
libpthread is given a version bump.
Reviewed by: davidxu
|
|
|
|
|
|
| |
is defined in the environment.
Requested by: jmg & a few others
|
|
|
|
|
|
|
| |
The thread jump table has been resorted, so you need to
keep libc, libpthread, and libthr in sync.
Submitted by: xu
|
|
|
|
|
|
| |
atomic operation to return and adjust the stack.
Submitted by: luoqi
|
|
|
|
|
|
| |
MFC Candidate.
PR: 93592
|
|
|
|
|
| |
MFC candidate
Noticed by: luoqi
|
|
|
|
|
|
| |
about to significantly increase the number of spinlocks used.
Approved by: markm (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add posix_memalign().
* Move calloc() from calloc.c to malloc.c. Add a calloc() implementation in
rtld-elf in order to make the loader happy (even though calloc() isn't
used in rtld-elf).
* Add _malloc_prefork() and _malloc_postfork(), and use them instead of
directly manipulating __malloc_lock.
Approved by: phk, markm (mentor)
|
|
|
|
|
|
|
|
|
|
| |
functions in the child after a fork() from a threaded process,
use __sys_setprocmask() rather than setprocmask() to keep our
signal handling sane. Without this fix, signals are essentially
ignored in said child and things such as protection violations
result in an endless busy loop.
Reviewed by: deischen
|
|
|
|
|
|
| |
o Make this ILP32/LP64 clean: cast pointers to long
o Code conditional upon DEBUG must also be conditional
upon _LIBC_R_
|
|
|
|
| |
o Make this ILP32/LP64 clean: cast pointers to long.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Don't reinitialise the atfork() handler list in the child. We
are meant to call the child handler, and on subsequent fork()s
should call all three functions as normal.
o Don't reinitialise the thread specific keyed data in the
child after a fork. Applications may require this for context.
o Reinitialise curthread->tlflags after removing ourselves from
(and reinitialising) the various internal thread lists.
o Reinitialise __malloc_lock in the child after fork() (to balance
our explicitly taking the lock prior to the fork()).
With these changes, it is possible to enable the NOTYET code in
thr_kern.c to allow the use of non-async-safe functions after
fork()ing from a threaded program.
Reviewed by: Daniel Eischen <deischen@freebsd.org>
[_malloc_lock reinitialisation has since been moved to avoid polluting the
!NOTYET code]
|
|
|
|
| |
while here.
|
|
|
|
|
|
| |
malloc() siginfo.
PR: 85468
|
|
|
|
| |
PR: 83457
|
|
|
|
| |
PR: 83452
|
|
|
|
|
|
| |
- Remove the macros MUTEX_TYPE_FAST and MUTEX_TYPE_COUNTING_FAST.
OK'ed by: deischen
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
been bumped since RELENG_5.
Reviewed by: ru
Approved by: re (not needed for commit check but in principle...)
|
|
|
|
|
|
|
|
| |
Like on libthr, there is an i386_set_gsbase() stub implementation here
to avoid libc.so.5 issues. This should likely be a weak symbol and I
expect this will be fixed soon.
Approved by: re
|
|
|
|
|
|
| |
Reviewed by: deischen
Approved by: re (dwhite)
MFC after : 4 days
|
|
|
|
|
| |
that the amd64 kernel implements i386_get/set_gsbase(). All the rest of
the ldt backwards compat code should go away soon.
|
|
|
|
|
| |
This is a little hairy here because the allocation and usage of this
functionality is split into two places in libpthread.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
the lock is held by other thread, but not when nobody owns it. According
to deischen@, this part of code will never be hit in our threads
library, since it does not use locks without wait/wakeup functions.
Spotted by: mingyanguo via ChinaUnix.net forum
Reviewed by: deischen
|
|
|
|
| |
ARM_TP_ADDRESS.
|
|
|
|
|
|
|
| |
changed to use the statclock. Make sure we calculate the value
of a tick correctly in userland.
Noticed by: Kazuaki Oda <kaakun at highway dot ne dot jp>
|
|
|
|
| |
attribute when the library is initialized.
|
|
|
|
|
|
| |
32-bit 64-bit
main thread 2MB 4MB
other threads 1MB 2MB
|
|
|
|
| |
PR: 75273
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
signals instead of having more intricate knowledge of thread state
within signal handling.
Simplify signal code because of above (by David Xu).
Use macros for libpthread usage of pthread_cleanup_push() and
pthread_cleanup_pop(). This removes some instances of malloc()
and free() from the semaphore and pthread_once() implementations.
When single threaded and forking(), make sure that the current
thread's signal mask is inherited by the forked thread.
Use private mutexes for libc and libpthread. Signals are
deferred while threads hold private mutexes. This fix also
breaks www/linuxpluginwrapper; a patch that fixes it is at
http://people.freebsd.org/~deischen/kse/linuxpluginwrapper.diff
Fix race condition in condition variables where handling a
signal (pthread_kill() or kill()) may not see a wakeup
(pthread_cond_signal() or pthread_cond_broadcast()).
In collaboration with: davidxu
|
|
|
|
|
| |
kernels. Use the recently exposed direct-set routines instead. This is
only activated for when we compile i386 support libraries on amd64.
|
| |
|
| |
|
|
|
|
|
|
|
| |
a thread in pthread_cond_wait handled a signal can no longer
be canceled.
Reviewed by: deischen
|
|
|
|
|
|
|
|
|
| |
packages expect and seems to be most correct according to the slightly-
ambiguous standards.
MFC after: 1 month
Corroborated by: POSIX <http://tinyurl.com/4uvub>
Reviewed by: silence on threads@
|
|
|
|
| |
any fake value.
|
|
|
|
|
| |
this reduces chances of signal losting problem found by
Peter Holm <peter@holm.cc>
|
|
|
|
|
|
|
|
|
|
|
| |
put DEAD thread on GC list, this closes a race between pthread_join
and thr_cleanup.
2. Introduce a mutex to protect tcb initialization, tls allocation and
deallocation code in rtld seems no lock protection or it is broken,
under stress testing, memory is corrupted.
Reviewed by: deischen
patch partly provided by: deischen
|
|
|
|
| |
leak under some cases.
|
|
|
|
|
|
| |
before and after sleeping.
Reviewed by: deischen
|
| |
|