[lkml]   [2004]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: UDP recvmsg blocks after select(), 2.6 bug?
On Wed, 6 Oct 2004, Richard B. Johnson wrote:

> thing --not. Select must return correct information.

It does, it's just state that select() reported on changed by the
time user called recvmsg.

> When a function call like select() says there are data available,
> there must be data available, period.

There was, but there wasnt when recvmsg() was called. Time changes

> If not, it's broken and needs to be fixed. Requiring one to set
> sockets to non-blocking is a poor work- around for an otherwise
> fatal flaw.

Any application that expects socket read not to block should set

> Cheers,
> Dick Johnson

Paul Jakma Key ID: 64A2FF6A
Kansas state law requires pedestrians crossing the highways at night to
wear tail lights.
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:06    [W:0.202 / U:15.064 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site