From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: "Dan Akunis" <dan.akunis@gmail.com>
Cc: <labbott@redhat.com>, "David Miller" <davem@davemloft.net>,
<kuznet@ms2.inr.ac.ru>, <jmorris@namei.org>,
<yoshfuji@linux-ipv6.org>, <kaber@trash.net>,
<samanthakumar@google.com>, <willemb@google.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] Select hang with zero sized UDP packets
Date: Wed, 24 Aug 2016 14:42:46 +0100 [thread overview]
Message-ID: <20160824144246.5a61254c@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <2ABF798B42E64D9C89DEB806A2E636B5@mtl.com>
On Wed, 24 Aug 2016 11:22:09 +0300
"Dan Akunis" <dan.akunis@gmail.com> wrote:
> When select wakes up on a UDP socket, user is expecting to get data. Getting
> 0 from recvfrom() or whatever read function she uses, is a wrong attitude.
> I agree with David.
>
> The unit test that expects select to wake up is wrong and should be changed.
The unit test is correct.
The behaviour of a 0 byte frame is actually well established and a 0 byte
data frame is a meaningful message is several protocols. It is distinct
from no pending data because that would report EWOULDBLOCK. It's more fun
with regard to EOF but UDP has no EOF semantics. If you want to
understand how to handle zero length datagrams in a connection oriented
protocol the old DECnet documentation covers it in all its pain 8)
Alan
prev parent reply other threads:[~2016-08-24 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 17:53 Laura Abbott
2016-08-23 18:25 ` David Miller
2016-08-23 19:03 ` Eric Dumazet
2016-08-23 20:06 ` Laura Abbott
2016-08-23 20:42 ` Eric Dumazet
2016-08-24 8:22 ` Dan Akunis
2016-08-24 13:02 ` Eric Dumazet
2016-08-24 13:42 ` One Thousand Gnomes [this message]
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=20160824144246.5a61254c@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=dan.akunis@gmail.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=samanthakumar@google.com \
--cc=willemb@google.com \
--cc=yoshfuji@linux-ipv6.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®