Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd

To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: bug-hurd@gnu.org, 752237@bugs.debian.org
Subject: Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd
From: Richard Braun <rbraun@sceen.net>
Date: Sat, 28 Jun 2014 14:52:42 +0200
Message-id: <[🔎] 20140628125242.GA10810@dalaran.sceen.net>
Reply-to: Richard Braun <rbraun@sceen.net>, 752237@bugs.debian.org
In-reply-to: <[🔎] 20140628104240.GA16870@dalaran.sceen.net>
References: <[🔎] 53A58F1E.8020902@googlemail.com> <[🔎] 20140628084856.GA24118@dalaran.sceen.net> <[🔎] 20140628095142.GA7179@dalaran.sceen.net> <[🔎] 20140628100915.GZ6351@type.youpi.perso.aquilenet.fr> <[🔎] 20140628104240.GA16870@dalaran.sceen.net>

On Sat, Jun 28, 2014 at 12:42:40PM +0200, Richard Braun wrote:
> I'll see if simply catching completely empty messages at socket_send is
> a good enough solution.

The solution seems to work, and I couldn't see anything against it,
unlike the previous attempt. However I'd really like to put it into
libpipe as I don't see any need, but only potential problems, for empty
data packets. I'll wait for your reply before taking action.

-- 
Richard Braun

Reply to:

References:
- Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd
  - From: Andreas Cadhalpun <andreas.cadhalpun@googlemail.com>
- Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd
  - From: Richard Braun <rbraun@sceen.net>
- Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd
  - From: Richard Braun <rbraun@sceen.net>
- Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd
  - From: Samuel Thibault <samuel.thibault@gnu.org>
- Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd
  - From: Richard Braun <rbraun@sceen.net>

Prev by Date: Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd
Next by Date: Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd
Previous by thread: Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd
Next by thread: Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd
Index(es):
- Date
- Thread