[Bug 215826] C++ program signal handlers not called
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Jan 10 19:27:12 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215826
--- Comment #6 from commit-hook at freebsd.org ---
A commit references this bug:
Author: kib
Date: Tue Jan 10 19:26:55 UTC 2017
New revision: 311886
URL: https://svnweb.freebsd.org/changeset/base/311886
Log:
Fix acquisition of nested write compat rtld locks.
Obtaining compat rtld lock in write mode sets process signal mask to
block all signals. Previous mask is stored in the global variable
oldsigmask. If a lock is write-locked while another lock is already
write-locked, oldsigmask is overwritten by the total mask and on the
last unlock, all signals except traps appear to be blocked.
Fix this by counting the write-lock nested level, and only storing to
oldsigmask/restoring from it at the outermost level.
Masking signals disables involuntary preemption for libc_r, and there
could be no voluntary context switches in the locked code
(dl_iterate_phdr(3) keeps a lock around user callback, but it was
added long after libc_r was renounced). Due to this, remembering the
level in the global variable after the lock is obtained should be
safe, because no two libc_r threads can acquire different write locks
in parallel.
PR: 215826
Reported by: kami
Tested by: yamagi at yamagi.org (previous version)
To be reviewed by: kan
Sponsored by: The FreeBSD Foundation
MFC after: 2 weeks
Changes:
head/libexec/rtld-elf/rtld_lock.c
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list