[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <9bede0ef7e66729034988f2d01681ca88a5c52d6.camel@infinera.com>
Date: Thu, 22 Oct 2020 15:19:36 +0000
From: Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
To: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: arping stuck with ENOBUFS in 4.19.150
strace arping -q -c 1 -b -U -I eth1 0.0.0.0
...
sendto(3, "\0\1\10\0\6\4\0\1\0\6\234\v\6 \v\v\v\v\377\377\377\377\377\377\0\0\0\0", 28, 0, {sa_family=AF_PACKET, proto=0x806, if4, pkttype=PACKET_HOST, addr(6)={1, ffffffffffff},
20) = -1 ENOBUFS (No buffer space available)
....
and then arping loops.
in 4.19.127 it was:
sendto(3, "\0\1\10\0\6\4\0\1\0\6\234\5\271\362\n\322\212E\377\377\377\377\377\377\0\0\0\0", 28, 0, {​sa_family=AF_PACKET, proto=0x806, if4, pkttype=PACKET_HOST, addr(6)={​1,
ffffffffffff}​, 20) = 28
Seems like something has changed the IP behaviour between now and then ?
eth1 is UP but not RUNNING and has an IP address.
Jocke
Powered by blists - more mailing lists