public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tom dot honermann at oracle dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/4737] fork is not async-signal-safe Date: Tue, 11 Nov 2008 22:04:00 -0000 [thread overview] Message-ID: <20081111220304.31614.qmail@sourceware.org> (raw) In-Reply-To: <20070704013541.4737.nmiell@comcast.net> ------- Additional Comments From tom dot honermann at oracle dot com 2008-11-11 22:03 ------- Another solution for this issue would be to use error checked mutexes (ie, PTHREAD_MUTEX_ERRORCHECK). However, glibc 2.3.4 doesn't seem to have a generic infrastructure for supporting error checked mutexes as it does for recursive mutexes (ie, __libc_lock_init vs __libc_lock_init_recursive - there is no __libc_lock_init_error_checked or similar that I can find), so this approach might require a more invasive change. If error checked mutexes were used, then ptmalloc_lock_all could be modified similarly to the code below. (This assumes mutex_lock would return the same values as pthread_mutex_lock) static void ptmalloc_lock_all (void) { mstate ar_ptr; int rc; if(__malloc_initialized < 1) return; rc = mutex_lock(&list_lock); if(rc != 0 && rc != EDEADLK) { /* Error handling */ } for(ar_ptr = &main_arena;;) { rc = mutex_lock(&ar_ptr->mutex); if(rc != 0 && rc != EDEADLK) { /* Error handling */ } ar_ptr = ar_ptr->next; if(ar_ptr == &main_arena) break; } save_malloc_hook = __malloc_hook; save_free_hook = __free_hook; __malloc_hook = malloc_atfork; __free_hook = free_atfork; /* Only the current thread may perform malloc/free calls now. */ tsd_getspecific(arena_key, save_arena); tsd_setspecific(arena_key, ATFORK_ARENA_PTR); } -- http://sourceware.org/bugzilla/show_bug.cgi?id=4737 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2008-11-11 22:04 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-04 1:35 [Bug libc/4737] New: " nmiell at comcast dot net 2008-10-11 18:47 ` [Bug libc/4737] " morten+sources dot redhat dot com at afdelingp dot dk 2008-10-20 11:47 ` morten+sources dot redhat dot com at afdelingp dot dk 2008-10-21 5:13 ` nmiell at comcast dot net 2008-10-30 14:55 ` morten+sources dot redhat dot com at afdelingp dot dk 2008-11-05 9:00 ` tom dot honermann at oracle dot com 2008-11-05 9:57 ` tom dot honermann at oracle dot com 2008-11-06 23:10 ` nmiell at comcast dot net 2008-11-07 1:10 ` morten+sources dot redhat dot com at afdelingp dot dk 2008-11-11 21:35 ` tom dot honermann at oracle dot com 2008-11-11 21:41 ` tom dot honermann at oracle dot com 2008-11-11 22:04 ` tom dot honermann at oracle dot com [this message] 2008-11-18 22:30 ` tom dot honermann at oracle dot com 2008-11-18 23:45 ` rsa at us dot ibm dot com 2008-11-18 23:57 ` rsa at us dot ibm dot com 2008-11-19 1:39 ` tom dot honermann at oracle dot com 2008-11-19 16:23 ` rsa at us dot ibm dot com 2009-01-14 1:22 ` tom dot honermann at oracle dot com 2009-01-14 8:46 ` jakub at redhat dot com 2009-01-14 9:44 ` tom dot honermann at oracle dot com 2009-01-16 17:19 ` tom dot honermann at oracle dot com [not found] <bug-4737-131@http.sourceware.org/bugzilla/> 2011-10-13 17:53 ` llucax at gmail dot com 2011-10-13 17:54 ` llucax at gmail dot com 2011-10-13 17:56 ` llucax at gmail dot com 2011-10-14 14:06 ` bugdal at aerifal dot cx 2012-03-27 13:43 ` krebbel1 at de dot ibm.com 2012-04-11 7:58 ` aj at suse dot de 2014-02-16 19:42 ` jackie.rosen at hushmail dot com 2014-05-28 19:41 ` schwab at sourceware dot org 2014-08-25 2:25 ` naesten at gmail dot com 2015-05-07 15:27 ` gbenson at redhat dot com 2021-06-28 19:00 ` adhemerval.zanella at linaro dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20081111220304.31614.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).