Re: read returns EAGAIN on a _blocking_ socket, but should not? (solved)

On Sun, Dec 25, 2005 at 04:16:11PM +0100, Marc Lehmann <[email protected]> wrote:
> Hi!
> 
> The SuS documents EAGAIN for read(2) as:

Argl, false alarm, very very sorry :(

>    sendmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\0", 1}], msg_controllen=20, {cmsg_len=20, cmsg_level=SOL_SOCKET, cmsg_type=SCM_RIGHTS, {3}}, msg_flags=MSG_OOB|MSG_DONTROUTE}, 0)                            = 1

Due to a bug, this sendmsg call passes the wrong fd (3), which the other
process then sets to non-blocking.

Again, sorry :(

-- 
                The choice of a
      -----==-     _GNU_
      ----==-- _       generation     Marc Lehmann
      ---==---(_)__  __ ____  __      [email protected]
      --==---/ / _ \/ // /\ \/ /      http://schmorp.de/
      -=====/_/_//_/\_,_/ /_/\_\      XX11-RIPE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- read returns EAGAIN on a _blocking_ socket, but should not?
  - From: Marc Lehmann <[email protected]>

Prev by Date: Re: [PATCH] - Fix memory ordering problem in wake_futex()
Next by Date: kernel list / container_of aka list_entry question
Previous by thread: read returns EAGAIN on a _blocking_ socket, but should not?
Next by thread: kernel list / container_of aka list_entry question
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]