On 10/29/2018 08:31 PM, John Fastabend wrote: > We return 0 in the case of a nonblocking socket that has no data > available. However, this is incorrect and may confuse applications. > After this patch we do the correct thing and return the error > EAGAIN. > > Quoting return codes from recvmsg manpage, > > EAGAIN or EWOULDBLOCK > The socket is marked nonblocking and the receive operation would > block, or a receive timeout had been set and the timeout expired > before data was received. > > Signed-off-by: John Fastabend <john.fastab...@gmail.com>
Applied to bpf, thanks!
