[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e09b367a58a0499f3bb0394596a9f87cc20eb5de.camel@infinera.com>
Date: Mon, 26 Oct 2020 12:58:16 +0000
From: Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
To: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: arping stuck with ENOBUFS in 4.19.150
Ping (maybe it should read "arping" instead :)
Jocke
On Thu, 2020-10-22 at 17:19 +0200, Joakim Tjernlund wrote:
> 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