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

Re: [PATCH] REFTABLE_REALLOC_ARRAY: fix potential memory leak if realloc failed

From
René Scharfe <l.s.r@web.de>
Date
May 8, 2025, 21:42 UTC
Message-ID
<174cb568-e2bd-41e0-b090-eadd919d1ddd@web.de>
In-Reply-To
<pull.1955.git.git.1746711583166.gitgitgadget@gmail.com>
Am 08.05.25 um 15:39 schrieb Lidong Yan via GitGitGadget:
> From: Lidong Yan <502024330056@smail.nju.edu.cn>
> 
> REFTABLE_REALLOC_ARRAY doesn't free origin pointer when reftable_realloc
> failed. This leak can be fixed by add a free(x) before set x to NULL.
Hmm, this macro is unused.  Perhaps remove it?
René
Previous: Lidong Yan via GitGitGadgetNext: lidongyan
Message 2 of 10 in “REFTABLE_REALLOC_ARRAY: fix potential memory leak if realloc failed”
  1. REFTABLE_REALLOC_ARRAY: fix potential memory leak if realloc failedLidong Yan via GitGitGadget, May 8, 2025
  2. René ScharfeMay 8, 2025
  3. lidongyanMay 9, 2025
  4. Junio C HamanoMay 9, 2025
  5. REFTABLE_REALLOC_ARRAY: remove this unsafe yet unused macroLidong Yan via GitGitGadget, May 9, 2025
  6. Patrick SteinhardtMay 9, 2025
  7. lidongyanMay 9, 2025
  8. REFTABLE_REALLOC_ARRAY: remove this unsafe yet unused macroLidong Yan via GitGitGadget, May 9, 2025
  9. Patrick SteinhardtMay 9, 2025
  10. Junio C HamanoMay 9, 2025

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.