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

[PATCH 0/5] coverity mixed bag

From
Jeff King <peff@peff.net>
Date
Jul 24, 2014, 04:39 UTC
Message-ID
<20140724043940.GA31282@peff.net>

Since Stefan has recently started feeding git builds to coverity, I spent a few minutes poking through the results. There are tons of false positives, so there is some work to be done there with tweaking our coverity models. But there are some real issues, too. Here are fixes for the handful that I looked at.

  [1/5]: receive-pack: don't copy "dir" parameter
  [2/5]: free ref string returned by dwim_ref
  [3/5]: transport: fix leaks in refs_from_alternate_cb
  [4/5]: fix memory leak parsing core.commentchar
  [5/5]: apply: avoid possible bogus pointer
-Peff
Next: Jeff King
Message 1 of 8 in “coverity mixed bag”
  1. 0/5 coverity mixed bagJeff King, Jul 24, 2014
  2. 1/5 receive-pack: don't copy "dir" parameterJeff King, Jul 24, 2014
  3. 2/5 free ref string returned by dwim_refJeff King, Jul 24, 2014
  4. 3/5 transport: fix leaks in refs_from_alternate_cbJeff King, Jul 24, 2014
  5. 4/5 fix memory leak parsing core.commentcharJeff King, Jul 24, 2014
  6. 5/5 apply: avoid possible bogus pointerJeff King, Jul 24, 2014
  7. Junio C HamanoJul 24, 2014
  8. Stefan BellerJul 29, 2014

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.