use libc-internal malloc for pthread_atfork
authorRich Felker <dalias@aerifal.cx>
Sat, 17 Dec 2022 21:00:19 +0000 (16:00 -0500)
committerRich Felker <dalias@aerifal.cx>
Sat, 17 Dec 2022 21:00:19 +0000 (16:00 -0500)
while no lock is held here making it a lock-order issue, replacement
malloc is likely to want to use pthread_atfork, possibly making the
call to malloc infinitely recursive.

even if not, there is no reason to prefer an application-provided
malloc here.


No differences found