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

Re: [PATCH] name-hash: fix buffer overrun

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 31, 2017, 19:35 UTC
Message-ID
<xmqqo9whxmrq.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170331173214.47514-2-git@jeffhostetler.com>
git@jeffhostetler.com writes:
Show 20 quoted lines
> From: Kevin Willford <kewillf@microsoft.com>
>
> Add check for the end of the entries for the thread partition.
> Add test for lazy init name hash with specific directory structure
>
> The lazy init hash name was causing a buffer overflow when the last
> entry in the index was multiple folder deep with parent folders that
> did not have any files in them.
>
> This adds a test for the boundary condition of the thread partitions
> with the folder structure that was triggering the buffer overflow.
>
> The fix was to check if it is the last entry for the thread partition
> in the handle_range_dir and not try to use the next entry in the cache.
>
> Signed-off-by: Kevin Willford <kewillf@microsoft.com>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com>
>
> ---
Will queue with ...
>  name-hash.c                             |  4 +++-
>  t/t3008-ls-files-lazy-init-name-hash.sh | 19 +++++++++++++++++++
>  2 files changed, 22 insertions(+), 1 deletion(-)
>  create mode 100644 t/t3008-ls-files-lazy-init-name-hash.sh
... this thing fixed by "chmod +x" (otherwise the tests won't start).
Thanks.
Previous: git@jeffhostetler.comNext: Junio C Hamano
Message 3 of 11 in “name-hash: fix buffer overrun”
  1. name-hash: fix buffer overrungit@jeffhostetler.com, Mar 31, 2017
  2. name-hash: fix buffer overrungit@jeffhostetler.com, Mar 31, 2017
  3. Junio C HamanoMar 31, 2017
  4. Junio C HamanoMar 31, 2017
  5. Junio C HamanoMar 31, 2017
  6. Junio C HamanoApr 1, 2017
  7. Johannes SchindelinApr 1, 2017
  8. Junio C HamanoApr 1, 2017
  9. contrib/git-resurrect.sh: do not write \t for HT in sed scriptsJunio C Hamano, Apr 1, 2017
  10. Jakub NarębskiApr 2, 2017
  11. Junio C HamanoApr 2, 2017

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.