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

Re: [PATCH 0/3] sha256/gcrypt fixes

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 31, 2023, 15:58 UTC
Message-ID
<xmqqy1iwyswr.fsf@gitster.g>
In-Reply-To
<20230731120808.1230210-1-e@80x24.org>
Eric Wong <e@80x24.org> writes:
> I noticed problems requiring patches 2 and 3 while eyeballing
> the code, but had to come up with the first one to fix
> SANITIZE=leak, first.
Thanks.
Show 8 quoted lines
>
> Eric Wong (3):
>   sha256/gcrypt: fix build with SANITIZE=leak
>   sha256/gcrypt: fix memory leak with SHA-256 repos
>   sha256/gcrypt: die on gcry_md_open failures
>
>  sha256/gcrypt.h | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
Previous: Eric Wong
Message 5 of 5 in “sha256/gcrypt fixes”
  1. 0/3 sha256/gcrypt fixesEric Wong, Jul 31, 2023
  2. 1/3 sha256/gcrypt: fix build with SANITIZE=leakEric Wong, Jul 31, 2023
  3. 2/3 sha256/gcrypt: fix memory leak with SHA-256 reposEric Wong, Jul 31, 2023
  4. 3/3 sha256/gcrypt: die on gcry_md_open failuresEric Wong, Jul 31, 2023
  5. Junio C HamanoJul 31, 2023

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.