git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Thread-safe xmalloc and xrealloc needs a recursive mutex

From
Fredrik Kuivinen <frekui@gmail.com>
Date
Apr 8, 2010, 08:42 UTC
Message-ID
<g2h4c8ef71004080142r5df32f10u66ebba19799804eb@mail.gmail.com>
In-Reply-To
<4BBD829B.8040700@viscovery.net>
On Thu, Apr 8, 2010 at 09:15, Johannes Sixt <j.sixt@viscovery.net> wrote:
Show 27 quoted lines
> From: Johannes Sixt <j6t@kdbg.org>
>
> The mutex used to protect object access (read_mutex) may need to be
> acquired recursively.  Introduce init_recursive_mutex() helper function
> in thread-utils.c that constructs a mutex with the PHREAD_MUTEX_RECURSIVE
> attribute.
>
> pthread_mutex_init() emulation on Win32 is already recursive as it is
> implemented on top of the CRITICAL_SECTION type, which is recursive.
>
>    http://msdn.microsoft.com/en-us/library/ms682530%28VS.85%29.aspx
>
> Add do-nothing compatibility wrappers for pthread_mutexattr* functions.
>
> Initial-version-by: Fredrik Kuivinen <frekui@gmail.com>
> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
> ---
> Am 4/7/2010 16:45, schrieb Fredrik Kuivinen:
>> We only need something like the following (on top of Nico's previous
>> patch). Warning: It hasn't even been compile tested on WIN32.
>
> Unfortunately, it doesn't build. This patch replaces the tip of
> nd/malloc-threading.
>
> BTW, your uses of strerror(errno) in init_recursive_mutex() were wrong
> (pthread functions do not set errno), but it is better in any case to
> avoid die() in this function.
Very true. Thanks.
- Fredrik
Previous: Johannes SixtNext: Junio C Hamano
Message 36 of 39 in “Make xmalloc and xrealloc thread-safe”
  1. 1/2 Make xmalloc and xrealloc thread-safeFredrik Kuivinen, Mar 23, 2010
  2. Shawn O. PearceMar 23, 2010
  3. Fredrik KuivinenMar 23, 2010
  4. Nicolas PitreMar 23, 2010
  5. Fredrik KuivinenMar 24, 2010
  6. Nicolas PitreMar 24, 2010
  7. Shawn PearceMar 24, 2010
  8. Junio C HamanoMar 24, 2010
  9. Nicolas PitreMar 24, 2010
  10. Shawn PearceMar 24, 2010
  11. Make xmalloc and xrealloc thread-safeNicolas Pitre, Mar 24, 2010
  12. Shawn O. PearceMar 24, 2010
  13. Nicolas PitreMar 24, 2010
  14. Junio C HamanoMar 24, 2010
  15. Junio C HamanoMar 24, 2010
  16. Fredrik KuivinenMar 27, 2010
  17. Nicolas PitreMar 27, 2010
  18. Fredrik KuivinenMar 31, 2010
  19. Make xmalloc and xrealloc thread-safeNicolas Pitre, Apr 7, 2010
  20. Shawn O. PearceApr 7, 2010
  21. Nicolas PitreApr 7, 2010
  22. Shawn PearceApr 7, 2010
  23. Nicolas PitreApr 7, 2010
  24. Shawn PearceApr 7, 2010
  25. Nicolas PitreApr 7, 2010
  26. Fredrik KuivinenApr 7, 2010
  27. Nicolas PitreApr 7, 2010
  28. Fredrik KuivinenApr 7, 2010
  29. Erik Faye-LundApr 7, 2010
  30. Nicolas PitreApr 7, 2010
  31. Sverre RabbelierApr 7, 2010
  32. Fredrik KuivinenApr 7, 2010
  33. Junio C HamanoApr 7, 2010
  34. Johannes SixtApr 7, 2010
  35. Thread-safe xmalloc and xrealloc needs a recursive mutexJohannes Sixt, Apr 8, 2010
  36. Fredrik KuivinenApr 8, 2010
  37. Junio C HamanoApr 7, 2010
  38. 2/2 Make sha1_to_hex thread-safeFredrik Kuivinen, Mar 23, 2010
  39. Johannes SixtMar 23, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.