[lkml]   [2004]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: UDP recvmsg blocks after select(), 2.6 bug?
    From: "Lars Marowsky-Bree" <>
    >> [ snip ]
    >> Also note the examples that Stevens gives. For instance, he explicitly
    >> checks for EWOULDBLOCK after a read on a nonblocking fd that has been
    >> reported readable by select().
    > The specs don't disagree with that. On a O_NONBLOCK socket, that is
    > allowed.

    No, it isn't. select() may not behave differently based on the O_NONBLOCK
    flag at the moment of the select() call. And if a call to recvmsg() with O_NONBLOCK
    cleared doesn't block and since it can't return EAGAIN, then I don't think a recvmsg()
    call with O_NONBLOCK set should return EAGAIN where something like
    EIO should have been returned otherwise.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:07    [W:0.033 / U:0.400 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site