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

[PATCH 0/1] oidmap: make entry cleanup explicit in oidmap_clear

From
Seyi Kufoiji <kuforiji98@gmail.com>
Date
Jan 15, 2026, 13:16 UTC
Message-ID
<20260115131634.51968-1-kuforiji98@gmail.com>
Hello,

This small patch improves the clarity and safety of oidmap cleanup by making entry destruction explicit in oidmap_clear().

Previously, oidmap_clear() implicitly relied on callers to understand how and when stored entries were freed. This change introduces an explicit cleanup path, making ownership and lifecycle of oidmap entries clearer and less error-prone.

In addition to the implementation change, unit tests are added to exercise the cleanup semantics and verify correct behavior during map teardown.

Thanks, Seyi

Seyi Kufoiji (1):
  oidmap: make entry cleanup explicit in oidmap_clear
 oidmap.c                | 23 ++++++++++++++++++++---
 oidmap.h                | 15 +++++++++++++++
 t/unit-tests/u-oidmap.c | 41 +++++++++++++++++++++++++++++++++++++++++
 3 files changed, 76 insertions(+), 3 deletions(-)
-- 
2.43.0
Next: Seyi Kufoiji
Message 1 of 2 in “oidmap: make entry cleanup explicit in oidmap_clear”
  1. 0/1 oidmap: make entry cleanup explicit in oidmap_clearSeyi Kufoiji, Jan 15, 2026
  2. 1/1 oidmap: make entry cleanup explicit in oidmap_clearSeyi Kufoiji, Jan 15, 2026

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.