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

[PATCH v2 0/3] Fix a race condition when reading loose refs

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Jun 19, 2013, 06:36 UTC
Message-ID
<1371623788-7227-1-git-send-email-mhagger@alum.mit.edu>
This is v2 of mh/loose-refs-race-with-pack-ref

I took Peff's suggestion to use gotos rather than an infinite loop in the last patch, which means that there is no need for the old patch 03/04.

Michael Haggerty (3):
  resolve_ref_unsafe(): extract function handle_missing_loose_ref()
  resolve_ref_unsafe(): handle the case of an SHA-1 within loop
  resolve_ref_unsafe(): close race condition reading loose refs
 refs.c | 106 ++++++++++++++++++++++++++++++++++++++++++++---------------------
 1 file changed, 72 insertions(+), 34 deletions(-)
-- 
1.8.3.1
Next: Michael Haggerty
Message 1 of 6 in “Fix a race condition when reading loose refs”
  1. 0/3 Fix a race condition when reading loose refsMichael Haggerty, Jun 19, 2013
  2. 1/3 resolve_ref_unsafe(): extract function handle_missing_loose_ref()Michael Haggerty, Jun 19, 2013
  3. 2/3 resolve_ref_unsafe(): handle the case of an SHA-1 within loopMichael Haggerty, Jun 19, 2013
  4. 3/3 resolve_ref_unsafe(): close race condition reading loose refsMichael Haggerty, Jun 19, 2013
  5. Jeff KingJun 19, 2013
  6. Junio C HamanoJun 19, 2013

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.