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

Re: [PATCH v3 0/2] reftable/writer: fix memory leak when write fails

From
Patrick Steinhardt <ps@pks.im>
Date
May 12, 2025, 14:34 UTC
Message-ID
<aCIG2W60WbZtW8Lu@pks.im>
In-Reply-To
<pull.1958.v3.git.git.1747054145.gitgitgadget@gmail.com>
On Mon, May 12, 2025 at 12:49:02PM +0000, Lidong Yan via GitGitGadget wrote:
Show 6 quoted lines
> Lidong Yan (2):
>   reftable/writer: fix memory leak when `padded_write()` fails
>   reftable/writer: fix memory leak when `writer_index_hash()` fails
> 
>  reftable/writer.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
Thanks, these look good to me.
Patrick
Previous: Lidong Yan via GitGitGadget
Message 8 of 8 in “reftable/writer: fix memory leak when `padded_write()` fails”
  1. reftable/writer: fix memory leak when `padded_write()` failsLidong Yan via GitGitGadget, May 10, 2025
  2. reftable/writer: fix memory leak if write failsLidong Yan via GitGitGadget, May 11, 2025
  3. Patrick SteinhardtMay 12, 2025
  4. lidongyanMay 12, 2025
  5. 0/2 reftable/writer: fix memory leak when write failsLidong Yan via GitGitGadget, May 12, 2025
  6. 1/2 reftable/writer: fix memory leak when `padded_write()` failsLidong Yan via GitGitGadget, May 12, 2025
  7. 2/2 reftable/writer: fix memory leak when `writer_index_hash()` failsLidong Yan via GitGitGadget, May 12, 2025
  8. Patrick SteinhardtMay 12, 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.