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

Re: fact-import: failed to apply delta

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Feb 10, 2009, 21:32 UTC
Message-ID
<alpine.LNX.1.00.0902101628140.19665@iabervon.org>
In-Reply-To
<20090210212539.GV30949@spearce.org>
On Tue, 10 Feb 2009, Shawn O. Pearce wrote:
Show 25 quoted lines
> Daniel Barkalow <barkalow@iabervon.org> wrote:
> > 
> > I think maybe there's aliasing in the delta base cache? If it recycled a 
> > struct packed_git, the cache would come up with a cached tree at offset 12 
> > of the packed_git at that address, but the pack used by that struct has 
> > changed.
> 
> Yup, that must be it.
>  
> > I don't see any reason that the situation couldn't arise where you start a
> > pack, look up an object in it while it's still open but the object isn't 
> > in the window, cache the delta base, end that packfile, eventually start a 
> > packfile that gets allocated in the space that was freed, produce a new 
> > delta against the object at exactly the same offset of the new pack (with 
> > the same address as the old pack), and go on happily until you try looking 
> > up this last delta and pull the wrong base out of the cache.
> > 
> > I don't see any code to flush the delta cache ever, but it's hard to get a 
> > new packed_git allocated at the address of a freed one, except by doing a 
> > lot of checkpoints in fast-import...
> 
> *ouch*.  I think you found it.
> 
> We should dump the cached_objects table in sha1_file.c during
> a checkpoint in fast-import.

No, that one's keyed by sha1, and doesn't get collisions; it's the delta_base_cache that's the issue; it's keyed by struct packed_git * and offset.

	-Daniel
*This .sig left intentionally blank*
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 12 of 24 in “fact-import: failed to apply delta”
  1. Daniel BarkalowFeb 10, 2009
  2. Johannes SchindelinFeb 10, 2009
  3. Shawn O. PearceFeb 10, 2009
  4. Daniel BarkalowFeb 10, 2009
  5. Shawn O. PearceFeb 10, 2009
  6. Daniel BarkalowFeb 10, 2009
  7. Shawn O. PearceFeb 10, 2009
  8. Daniel BarkalowFeb 10, 2009
  9. Shawn O. PearceFeb 10, 2009
  10. Daniel BarkalowFeb 10, 2009
  11. Shawn O. PearceFeb 10, 2009
  12. Daniel BarkalowFeb 10, 2009
  13. Shawn O. PearceFeb 10, 2009
  14. Daniel BarkalowFeb 10, 2009
  15. Junio C HamanoFeb 10, 2009
  16. Junio C HamanoFeb 10, 2009
  17. Shawn O. PearceFeb 10, 2009
  18. Junio C HamanoFeb 10, 2009
  19. Shawn O. PearceFeb 10, 2009
  20. Junio C HamanoFeb 10, 2009
  21. Daniel BarkalowFeb 11, 2009
  22. Shawn O. PearceFeb 11, 2009
  23. Junio C HamanoFeb 11, 2009
  24. Daniel BarkalowFeb 11, 2009

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.