Re: UDP sockets oddities

From: Eric Dumazet <redacted>
Date: Fri, 25 Aug 2017 20:40:44 -0700

On Fri, 2017-08-25 at 20:25 -0700, Florian Fainelli wrote:

quoted

It would. Since the call trace involves udp_send_skb() how come we are
not returning an error to write(2)? are there other code paths where the
neighbor code can do drops like these?

Are you suggesting write(2) should block until ARP resolution is
done ? :)

What about non blocking writes ?

Honestly UDP is not a protocol for which we must absolutely be sure
packets are sent or not.

Agreed, but the ARP resolution queue really needs to scale it's backlog
to the physical technology it is attached to.