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

Re: [PATCH] diff: fix textconv error zombies

From
Jeff King <peff@peff.net>
Date
Mar 30, 2010, 22:56 UTC
Message-ID
<20100330225628.GB608@coredump.intra.peff.net>
In-Reply-To
<201003310017.24979.j6t@kdbg.org>
On Wed, Mar 31, 2010 at 12:17:24AM +0200, Johannes Sixt wrote:
Show 6 quoted lines
> This could deadlock in the theoretical case that the read() in the parent 
> returns an error even though the child is still writing data; the child would 
> hang while waiting for the pipe being drained by the parent; but the parent 
> would wait for the child to exit, which never happens. Doing the close() 
> before finish_command() avoids this situation because the child dies of 
> SIGPIPE.

Yeah, I actually thought about that while writing the error case for strbuf_read (I do close(child.out) before finish_command). But I didn't consider it in the success case. I don't think it matters here because we will already have gotten EOF from child.out, which should mean the child is no longer writing and will not block.

So I am not sure there is any deadlock, but I am fine with your version of the patch.

-Peff
Previous: Johannes SixtNext: Michael J Gruber
Message 10 of 19 in “fast textconv”
  1. 0/3 fast textconvJeff King, Mar 28, 2010
  2. 1/3 textconv: refactor calls to run_textconvJeff King, Mar 28, 2010
  3. 2/3 textconv: refactor to handle multiple textconv typesJeff King, Mar 28, 2010
  4. 3/3 diff: add "fasttextconv" config optionJeff King, Mar 28, 2010
  5. Johannes SixtMar 28, 2010
  6. Jeff KingMar 30, 2010
  7. diff: fix textconv error zombiesJohannes Sixt, Mar 30, 2010
  8. Junio C HamanoMar 30, 2010
  9. Johannes SixtMar 30, 2010
  10. Jeff KingMar 30, 2010
  11. Michael J GruberMar 28, 2010
  12. Jeff KingMar 28, 2010
  13. Jeff KingMar 28, 2010
  14. Jeff KingMar 28, 2010
  15. Jeff KingMar 28, 2010
  16. Sverre RabbelierMar 28, 2010
  17. Jeff KingMar 30, 2010
  18. Junio C HamanoMar 30, 2010
  19. Jeff KingMar 30, 2010

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.