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

[PATCH] reset slab_alloc and state fields in clear_alloc_state()

From
ノウラ | Flare via GitGitGadget <gitgitgadget@gmail.com>
Date
Aug 26, 2025, 19:57 UTC
Message-ID
<pull.2040.git.git.1756238268790.gitgitgadget@gmail.com>
From: =?UTF-8?q?=E3=83=8E=E3=82=A6=E3=83=A9?= <nea@odoo.com>

clear_alloc_state() freed all slabs and nulled the slabs pointer but left slab_alloc, nr, and p unchanged. If the alloc_state is reused, ALLOC_GROW() can wrongly assume that the slab array is already allocated because slab_alloc still holds a stale nonzero capacity. In that case s->slabs remains NULL and the next dereference writes through a NULL pointer, causing undefined behavior.

To fix this, we reset slab_alloc, nr, and p to zero/NULL after freeing the slabs. This leaves alloc_state in a consistent empty state for reuse and avoids dangling pointers.

Signed-off-by: Noura EL ALLAM <nouraellm@gmail.com>
---
    Reset slab_alloc and state fields in clear_alloc_state()
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2040%2Fnouraellm%2Ffix-dangling-pointer-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2040/nouraellm/fix-dangling-pointer-v1
Pull-Request: https://github.com/git/git/pull/2040
 alloc.c | 3 +++
 1 file changed, 3 insertions(+)
diff --git a/alloc.c b/alloc.c
index 377e80f5dda..6bf9421c123 100644
--- a/alloc.c
+++ b/alloc.c
@@ -49,6 +49,9 @@ void clear_alloc_state(struct alloc_state *s)
 	}
 
 	FREE_AND_NULL(s->slabs);
+	s->slab_alloc = 0;
+	s->nr = 0;
+	s->p = NULL;
 }
 
 static inline void *alloc_node(struct alloc_state *s, size_t node_size)

base-commit: f814da676ae46aac5be0a98b99373a76dee6cedb
-- 
gitgitgadget
Next: Junio C Hamano
Message 1 of 28 in “reset slab_alloc and state fields in clear_alloc_state()”
  1. reset slab_alloc and state fields in clear_alloc_state()ノウラ | Flare via GitGitGadget, Aug 26, 2025
  2. Junio C HamanoAug 27, 2025
  3. alloc: fix dangling pointer in alloc_state cleanupノウラ | Flare via GitGitGadget, Aug 27, 2025
  4. Torsten BögershausenAug 28, 2025
  5. Junio C HamanoAug 28, 2025
  6. Junio C HamanoAug 28, 2025
  7. alloc: fix dangling pointer in alloc_state cleanupノウラ | Flare via GitGitGadget, Aug 29, 2025
  8. Jeff KingSep 3, 2025
  9. Junio C HamanoSep 3, 2025
  10. alloc: fix dangling pointer in alloc_state cleanupノウラ | Flare via GitGitGadget, Sep 3, 2025
  11. Junio C HamanoSep 4, 2025
  12. ノウラ | FlareSep 4, 2025
  13. Junio C HamanoSep 4, 2025
  14. alloc: fix dangling pointer in alloc_state cleanupノウラ | Flare via GitGitGadget, Sep 4, 2025
  15. Junio C HamanoSep 4, 2025
  16. Jeff KingSep 4, 2025
  17. Junio C HamanoSep 4, 2025
  18. ノウラ | FlareSep 5, 2025
  19. Jeff KingSep 5, 2025
  20. ノウラ | FlareSep 5, 2025
  21. ノウラ | FlareSep 5, 2025
  22. ノウラ | FlareSep 5, 2025
  23. ノウラ | FlareSep 5, 2025
  24. Junio C HamanoSep 5, 2025
  25. ノウラ | FlareSep 5, 2025
  26. Jeff KingSep 5, 2025
  27. alloc: fix dangling pointer in alloc_state cleanupノウラ | Flare via GitGitGadget, Sep 5, 2025
  28. Junio C HamanoSep 5, 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.