This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glibc 2.26 deadlock with __resolv_conf_detach


On Sep 19 2019, Douglas Jacobsen <dmjacobsen@lbl.gov> wrote:

> The scenario we've uncovered is that some vendor software runs a
> multithreaded daemon, which then fork()s, and spawns a thread,

In the forked child?  If a multi-threaded process calls fork, the child
may only call async-signal-safe functions.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]