On Wed, Feb 21, 2018 at 1:26 AM, Martin Pieuchot <[email protected]> wrote:
> Is it safe? What kind of deadlock/weird situation can occur? > > I'm asking because the diff below, that introduces a lock to protect uid > globals, has an XXX comment from guenther@ asking if it is a problem. > The unclarity of concision: the question behind the XXX was whether the code should release uidinfolk before the free() and then reacquire it, as holding uidinfolk blocks all (real) UID changing calls as well as waitpid(), fork(), and __tfork(). Could free() be so slow that not blocking those could be a concern? Doubtful, but <shrug> Philip
