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

Re: git-upload-pack: the timeout gets corrupted?!

From
HAH. Peter Anvin <hpa@zytor.com>
Date
Mar 11, 2007, 09:23 UTC
Message-ID
<45F3CAAF.7030909@zytor.com>
In-Reply-To
<7vy7m4wcfb.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
Show 10 quoted lines
> 
>> The process spends effectively forever waiting in on the fflush() in
>> show_commit() (in upload-pack.c); /proc/*/fd shows it is trying to
>> write to a pipe, but I'm not sure what is at the other end of that
>> same pipe.
> 
> The process forks and the one that runs show_commit() is running
> rev-list internally while the other end is a pack-objects that
> reads from it and sends its output back to the client.
> 

Now, given that the fact that the git-pack-object process has already died, normally one would expect the write() to get SIGPIPE which would kill the process. Does git-upload-pack not close the read end of the pipe in the writer? From the looks of the fd directory, I would say it does not.

	-hpa
Previous: H. Peter AnvinNext: Johannes Schindelin
Message 4 of 10 in “git-upload-pack: the timeout gets corrupted?!”
  1. H. Peter AnvinMar 11, 2007
  2. Junio C HamanoMar 11, 2007
  3. H. Peter AnvinMar 11, 2007
  4. H. Peter AnvinMar 11, 2007
  5. Johannes SchindelinMar 11, 2007
  6. H. Peter AnvinMar 11, 2007
  7. Johannes SchindelinMar 11, 2007
  8. H. Peter AnvinMar 11, 2007
  9. H. Peter AnvinMar 11, 2007
  10. H. Peter AnvinMar 11, 2007

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.