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

Re: [PATCH v2 1/2] t: add a test helper to truncate files

From
Jeff King <peff@peff.net>
Date
Oct 16, 2023, 23:53 UTC
Message-ID
<20231016235333.GA551672@coredump.intra.peff.net>
In-Reply-To
<20231012160930.330618-2-sandals@crustytoothpaste.net>
On Thu, Oct 12, 2023 at 04:09:29PM +0000, brian m. carlson wrote:
Show 21 quoted lines
> +int cmd__truncate(int argc, const char **argv)
> +{
> +	char *p = NULL;
> +	uintmax_t sz = 0;
> +	int fd = -1;
> +
> +	if (argc != 3)
> +		die("expected filename and size");
> +
> +	sz = strtoumax(argv[2], &p, 0);
> +	if (*p)
> +		die("invalid size");
> +
> +	fd = open(argv[1], O_WRONLY | O_CREAT, 0600);
> +	if (fd < 0)
> +		die_errno("failed to open file %s", argv[1]);
> +
> +	if (ftruncate(fd, (off_t) sz) < 0)
> +		die_errno("failed to truncate file");
> +	return 0;
> +}

Coverity flagged this as leaking the descriptor "fd" (which is obviously true). I guess it doesn't matter much in practice, since we're exiting the process directly afterwards. If it were a memory leak we'd free() it anyway to shut up the leak detector, but I don't know if we want to be as careful here (in theory it creates noise that distracts from real problems, but Coverity is noisy enough that I don't even bother looking at existing problems).

-Peff
Previous: Junio C HamanoNext: brian m. carlson
Message 8 of 16 in “Prevent re-reading 4 GiB files on every status”
  1. 0/2 Prevent re-reading 4 GiB files on every statusbrian m. carlson, Oct 12, 2023
  2. 1/2 t: add a test helper to truncate filesbrian m. carlson, Oct 12, 2023
  3. Eric SunshineOct 12, 2023
  4. brian m. carlsonOct 13, 2023
  5. Junio C HamanoOct 12, 2023
  6. brian m. carlsonOct 13, 2023
  7. Junio C HamanoOct 13, 2023
  8. Jeff KingOct 16, 2023
  9. 2/2 Prevent git from rehashing 4GiB filesbrian m. carlson, Oct 12, 2023
  10. Junio C HamanoOct 12, 2023
  11. brian m. carlsonOct 12, 2023
  12. Junio C HamanoOct 12, 2023
  13. Jeff KingOct 17, 2023
  14. Jason HattonOct 17, 2023
  15. Junio C HamanoOct 17, 2023
  16. brian m. carlsonOct 18, 2023

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.