This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [patch] Fix for bz14333 -- race between atexit() and exit()
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Paul Pluzhnikov <ppluzhnikov at google dot com>
- Cc: GLIBC Devel <libc-alpha at sourceware dot org>, Anoop V Chakkalakkal <anoop dot vijayan at in dot ibm dot com>
- Date: Tue, 11 Jul 2017 12:22:30 +0000
- Subject: Re: [patch] Fix for bz14333 -- race between atexit() and exit()
- Authentication-results: sourceware.org; auth=none
- References: <CALoOobNCZqgvcLJhuJt5eSWseuTfHJ9oVsG9TpPvytyfzF56mg@mail.gmail.com>
On Mon, 10 Jul 2017, Paul Pluzhnikov wrote:
> Greetings,
>
> This patch is an update to previous patch by Anoop:
> https://sourceware.org/ml/libc-alpha/2008-09/msg00013.html
>
> See discussion in the above message.
>
> Changes from the previous patch: I extended the lifetime of the lock
> from __new_exitfn to its callers, since they *also* modify global
> state.
Is there such a race for quick_exit / at_quick_exit (which postdate the
previous patch), or not? If there is, it should also be fixed (all
atexit-like functions should be fixed).
Is it possible to add a test / tests for this issue to the glibc
testsuite?
--
Joseph S. Myers
joseph@codesourcery.com