Adhemerval Zanella c32c868ab8 posix: Add _Fork [BZ #4737]
Austin Group issue 62 [1] dropped the async-signal-safe requirement
for fork and provided a async-signal-safe _Fork replacement that
does not run the atfork handlers.  It will be included in the next
POSIX standard.

It allow to close a long standing issue to make fork AS-safe (BZ#4737).
As indicated on the bug, besides the internal lock for the atfork
handlers itself; there is no guarantee that the handlers itself will
not introduce more AS-safe issues.

The idea is synchronize fork with the required internal locks to allow
children in multithread processes to use mostly of standard function
(even though POSIX states only AS-safe function should be used).  On
signal handles, _Fork should be used intead and only AS-safe functions
should be used.

For testing, the new tst-_Fork only check basic usage.  I also added
a new tst-mallocfork3 which uses the same strategy to check for
deadlock of tst-mallocfork2 but using threads instead of subprocesses
(and it does deadlock if it replaces _Fork with fork).

[1] https://austingroupbugs.net/view.php?id=62
2021-06-28 15:55:56 -03:00
..
2021-06-24 10:02:06 -03:00
2021-01-04 08:42:25 -03:00
2021-01-04 09:02:39 -03:00
2021-06-28 15:55:56 -03:00
2021-01-04 08:41:53 -03:00
2021-06-28 15:55:56 -03:00
2021-01-04 08:38:52 -03:00
2021-02-09 16:58:16 -03:00
2021-06-28 15:55:56 -03:00
2021-06-15 10:42:11 -03:00
2021-04-15 11:32:40 -03:00
2021-06-15 10:42:11 -03:00
2021-04-15 11:32:40 -03:00
2021-04-15 11:32:40 -03:00
2021-06-28 15:55:56 -03:00
2021-06-28 15:55:56 -03:00