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

Re: EAGAIN?

From
Linus Torvalds <torvalds@osdl.org>
Date
Dec 19, 2005, 19:46 UTC
Message-ID
<Pine.LNX.4.64.0512191142410.4827@g5.osdl.org>
In-Reply-To
<7vhd95h02o.fsf@assigned-by-dhcp.cox.net>
On Mon, 19 Dec 2005, Junio C Hamano wrote:
> 
> I was looking at "git grep -n EAGAIN" output and found that many
> places check "errno == EAGAIN" without checking "errno ==
> EINTR", both for read(2) and write(2).
I suspect it's mostly in my code. It's a stupid quirk of mine.

You might as well delete those thing, but yes, if you want to replace them with testing both EAGAIN and EINTR, go right ahead.

			Linus
Previous: Junio C HamanoNext: H. Peter Anvin
Message 2 of 6 in “EAGAIN?”
  1. Junio C HamanoDec 19, 2005
  2. Linus TorvaldsDec 19, 2005
  3. H. Peter AnvinDec 19, 2005
  4. xread/xwrite: do not worry about EINTR at calling sites.Junio C Hamano, Dec 20, 2005
  5. Johannes SchindelinDec 20, 2005
  6. Linus TorvaldsDec 20, 2005

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.