Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | test-skeleton.c: Add write_message function | Florian Weimer | 2016-06-23 | 1 | -11/+3 |
| | |||||
* | tst-mallocfork2: Fix race condition, use fewer resources | Florian Weimer | 2016-05-13 | 1 | -1/+7 |
| | | | | | | | | | | | | | | | | The first SIGUSR1 signal could arrive when sigusr1_sender_pid was still 0. As a result, kill would send SIGSTOP to the entire process group. This would cause the test to hang before printing any output. This commit also adds a sched_yield to the signal source, so that it does not flood the parent process with signals it has never a chance to handle. Even with these changes, tst-mallocfork2 still fails reliably after the fix in commit commit 56290d6e762c1194547e73ff0b948cd79d3a1e03 (Increase fork signal safety for single-threaded processes) is backed out. | ||||
* | Increase fork signal safety for single-threaded processes [BZ #19703] | Florian Weimer | 2016-05-12 | 1 | -0/+212 |
This provides a band-aid and addresses the scenario where fork is called from a signal handler while the process is in the malloc subsystem (or has acquired the libio list lock). It does not address the general issue of async-signal-safety of fork; multi-threaded processes are not covered, and some glibc subsystems have fork handlers which are not async-signal-safe. |