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

Re: [PATCH 2/2] format-patch: fix leak of rev_info in prepare_bases()

From
Jeff King <peff@peff.net>
Date
Jul 2, 2026, 08:58 UTC
Message-ID
<20260702085821.GC481298@coredump.intra.peff.net>
In-Reply-To
<akTXYoY7mSQUM33P@pks.im>
On Wed, Jul 01, 2026 at 11:01:22AM +0200, Patrick Steinhardt wrote:
Show 11 quoted lines
> > > linux-reftable or linux-reftable-leaks? I think it would certainly make
> > > sense to drop one of these and merge it into linux-TEST-vars. The
> > > linux-reftable job doesn't provide any benefit over its -leak variant,
> > > so that would be the candidate I'd personally merge.
> > 
> > Both. Fold linux-reftable into linux-TEST-vars, and then drop
> > linux-reftable-leaks in favor of a new linux-TEST-vars-leaks.
> 
> Hm, okay. I guess that should be fine. Do we also want to do a similar
> thing for macOS and create a macos-TEST-vars job that exercises all of
> this?

It could be helpful if we expect the interaction of macOS and those test-vars to be interesting, but I'm a bit skeptical. Most of them are about feature selection. So I'm doubtful it would turn up anything useful. But who knows.

Likewise I find the dual clang/gcc jobs to be overkill. Compiling with both is useful, as they have different warnings. But have we ever seen a case where running the tests showed a different result with different compilers?

I dunno. I guess there is an argument for CI-maximalism; as long as the jobs run in parallel and they're "just" CPU-minutes. But those minutes eventually have a cost, and I'm not sure I've gotten useful data from most of the jobs (i.e., failures that didn't also just happen somewhere else).

Anyway, that is all a big tangent/rant. Mostly I think it would be fine to cannibalize linux-reftable into linux-TEST-vars if we want to get more coverage without increasing the CI cost.

Note that I did find some leaks that would only be hit running linux-sha256 with a non-standard backend like OPENSSL_SHA256=1. But that is getting super specific now (even if we ran linux-sha256 with leak detection, would we want to do it with openssl and not the default backend)?

> Also, while at it... I really think that job name is just plain awful.
> While at it, we might rename it to something more sensible like
> "linux-changed-defaults".

Yes please. Every time I see the all-caps TEST in the middle I think I'm having a stroke.

change-defaults is OK but not super descriptive. I might call it linux-exotic-flags or something. That's not descriptive either, but is a little more fun.

-Peff
Previous: Patrick SteinhardtNext: Patrick Steinhardt
Message 9 of 15 in “small leak fix in format-patch”
  1. 0/2 small leak fix in format-patchJeff King, Jun 30, 2026
  2. 1/2 t: move LSan errors from stdout to stderrJeff King, Jun 30, 2026
  3. 2/2 format-patch: fix leak of rev_info in prepare_bases()Jeff King, Jun 30, 2026
  4. Patrick SteinhardtJun 30, 2026
  5. Jeff KingJul 1, 2026
  6. Patrick SteinhardtJul 1, 2026
  7. Jeff KingJul 1, 2026
  8. Patrick SteinhardtJul 1, 2026
  9. Jeff KingJul 2, 2026
  10. Patrick SteinhardtJul 2, 2026
  11. Junio C HamanoJul 3, 2026
  12. Jeff KingJul 6, 2026
  13. Patrick SteinhardtJul 6, 2026
  14. Karthik NayakJul 4, 2026
  15. Jeff KingJul 6, 2026

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.