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

Re: [PATCH 03/14] fetch-pack: defensive programming

From
Junio C Hamano <gitster@pobox.com>
Date
May 15, 2025, 17:24 UTC
Message-ID
<xmqqzffdzt0s.fsf@gitster.g>
In-Reply-To
<9cafbd36817aabbe18197938c409edaddf7dcab2.1747313140.git.gitgitgadget@gmail.com>

"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com> writes:

Show 20 quoted lines
> From: Johannes Schindelin <johannes.schindelin@gmx.de>
>
> CodeQL points out that `parse_object()` can return NULL values.
>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
>  fetch-pack.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fetch-pack.c b/fetch-pack.c
> index 1ed5e11dd568..4cbcb0c14c48 100644
> --- a/fetch-pack.c
> +++ b/fetch-pack.c
> @@ -155,7 +155,7 @@ static struct commit *deref_without_lazy_fetch(const struct object_id *oid,
>  			struct tag *tag = (struct tag *)
>  				parse_object(the_repository, oid);
>  
> -			if (!tag->tagged)
> +			if (!tag || !tag->tagged)
>  				return NULL;

The "oid" can come from corruptible sources like commit graph file, so I agree with your analysis that it may name a missing object in a corrupt repository, leading "tag" being NULL. Looks correct.

>  			if (mark_tags_complete_and_check_obj_db)
>  				tag->object.flags |= COMPLETE;
Previous: Johannes Schindelin via GitGitGadgetNext: Johannes Schindelin via GitGitGadget
Message 8 of 19 in “Some defensive programming”
  1. 00/14 Some defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  2. 01/14 revision: defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  3. Junio C HamanoMay 15, 2025
  4. 02/14 get_parent(): defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  5. Junio C HamanoMay 15, 2025
  6. Jeff KingMay 15, 2025
  7. 03/14 fetch-pack: defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  8. Junio C HamanoMay 15, 2025
  9. 04/14 unparse_commit(): defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  10. 05/14 verify_commit_graph(): defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  11. 06/14 stash: defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  12. 07/14 stash: defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  13. 08/14 push: defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  14. 09/14 fetch: defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  15. 10/14 describe: defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  16. 11/14 inherit_tracking(): defensive programmingJohannes Schindelin via GitGitGadget, May 15, 2025
  17. 12/14 submodule: check return value of `submodule_from_path()`Johannes Schindelin via GitGitGadget, May 15, 2025
  18. 13/14 test-tool repository: check return value of `lookup_commit()`Johannes Schindelin via GitGitGadget, May 15, 2025
  19. 14/14 shallow: handle missing shallow commits gracefullyJohannes Schindelin via GitGitGadget, May 15, 2025

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.