From: "David S. Miller" <davem@davemloft.net>
To: alan@lxorguk.ukuu.org.uk
Cc: kern@sibbald.com, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: blocking read on socket repeatedly returns EAGAIN
Date: Tue, 16 Aug 2005 11:37:28 -0700 (PDT) [thread overview]
Message-ID: <20050816.113728.44187103.davem@davemloft.net> (raw)
In-Reply-To: <1124200991.17555.33.camel@localhost.localdomain>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: Tue, 16 Aug 2005 15:03:11 +0100
> You are describing behaviour as expected with nonblocking set. That
> suggests to me that something or someone set or inherited the nonblock
> flag on that socket. Is the strange behaviour specific to the latest
> kernel ?
He could be receiving a signal Alan, look at tcp_recvmsg(),
it returns -EAGAIN and always has when a signal is delivered
to the reading process.
next prev parent reply other threads:[~2005-08-16 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 13:19 Kern Sibbald
2005-08-16 14:03 ` Alan Cox
2005-08-16 14:12 ` Kern Sibbald
2005-08-16 14:52 ` Alan Cox
2005-08-16 14:38 ` Kern Sibbald
2005-08-16 18:39 ` David S. Miller
2005-08-16 21:06 ` Kern Sibbald
2005-08-16 18:37 ` David S. Miller [this message]
2005-08-16 18:36 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050816.113728.44187103.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kern@sibbald.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®