This is the mail archive of the
mailing list for the glibc project.
Re: glibc 2.26 deadlock with __resolv_conf_detach
On Sep 19 2019, Douglas Jacobsen <firstname.lastname@example.org> wrote:
> Would the mechanism of failure here be that the lock variable in
> glibc/resolv/resolv_conf.c is already locked in the parent process at
> the time of fork()
Yes, that is the most likely cause. Since fork only duplicates the
calling thread, there will be nothing left to release the lock.
Andreas Schwab, SUSE Labs, email@example.com
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."