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

[PATCH 0/3] fix unparsed object access in upload-pack

From
Jeff King <peff@peff.net>
Date
Mar 16, 2013, 10:24 UTC
Message-ID
<20130316102428.GA29358@sigill.intra.peff.net>

This series fixes the issue I mentioned recently with upload-pack, where we might feed unparsed objects to the revision parser. The bug is in 435c833 (the tip of the jk/peel-ref topic), which is in v1.8.1 and up.

The fix should go to maint. The bug breaks shallow clones from repositories with packed refs, though the effects range from working OK to sending too many objects to calling die() in the revision traversal machinery. Given the size of the breakage (I had several bug reports within a few hours of deploying v1.8.1.5 on github.com), and the fact that the bug was introduced only in v1.8.1, it may make sense to roll a v1.8.1.6 in addition to putting it on the 1.8.2 maint track.

  [1/3]: upload-pack: drop lookup-before-parse optimization
    This is just a cleanup, and is not necessary for the fix.
  [2/3]: upload-pack: make sure "want" objects are parsed
    This is the fix itself, which can stand alone from the other two
    patches, both semantically and textually.
  [3/3]: upload-pack: load non-tip "want" objects from disk
    While investigating the bug, I found some weirdness around the
    stateless-rpc check_non_tip code. As far as I can tell, that code
    never actually gets triggered. It's not too surprising that we
    wouldn't have noticed, because it is about falling back due to a
    race condition. But please sanity check my explanation and patch.
-Peff
Next: Jeff King
Message 1 of 9 in “fix unparsed object access in upload-pack”
  1. 0/3 fix unparsed object access in upload-packJeff King, Mar 16, 2013
  2. 1/3 upload-pack: drop lookup-before-parse optimizationJeff King, Mar 16, 2013
  3. 2/3 upload-pack: make sure "want" objects are parsedJeff King, Mar 16, 2013
  4. 3/3 upload-pack: load non-tip "want" objects from diskJeff King, Mar 16, 2013
  5. Junio C HamanoMar 17, 2013
  6. Jeff KingMar 17, 2013
  7. Junio C HamanoMar 17, 2013
  8. Jeff KingMar 17, 2013
  9. René ScharfeMar 17, 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.