On Sat, 9 Jun 2018 02:04:38 -0400 Jeff King <peff@xxxxxxxx> wrote: > This function used to be idempotent, so any code which wanted to use the > global bitmap_git could call it "just in case". After your patch, it's > not. I think it's probably OK, since such functions would generally now > take a bitmap_git argument and use that (e.g., rebuild_existing_bitmaps > works that way after your patch). Yes, and I've checked that the existing callers do not use bitmaps twice. I've appended an extra paragraph for the commit message to this e-mail below that will hopefully clarify things. > We probably need to free(bitmap_git) before returning NULL here (this is > still in prepare_bitmap_git()). [snip] > Ditto here (and probably other error returns lower in the function, but > I didn't go through it carefully). The contents of the struct also need to be handled, and I wanted to handle it all at once in the subsequent patch. But you're right that the commit message should explain that. Here's an paragraph to be added to the end of the commit message. I can send a reroll with the exact same code but with the updated commit message if Junio requests it. [additional paragraph begin] This patch raises two potential issues: (1) memory for the struct bitmap_index is allocated without being freed, and (2) prepare_bitmap_git() and prepare_bitmap_walk() can reuse a previously loaded bitmap. For (1), this will be dealt with in a subsequent patch in this patch set that also deals with freeing the contents of the struct bitmap_index (which were not freed previously, because they have global scope). For (2), current bitmap users only load the bitmap once at most (note that pack-objects can use bitmaps or write bitmaps, but not both at the same time), so support for reuse has no effect - and future users can pass around the struct bitmap_index * obtained if they need to do 2 or more things with the same bitmap. [additional paragraph end]
