Re: arping stuck with ENOBUFS in 4.19.150

2020-11-02 Thread Joakim Tjernlund
On Sat, 2020-10-31 at 09:48 +0800, Yunsheng Lin wrote: > On 2020/10/30 19:50, Joakim Tjernlund wrote: > > On Fri, 2020-10-30 at 09:36 +0800, Yunsheng Lin wrote: > > > CAUTION: This email originated from outside of the organization. Do not > > > click links or open attachments unless you recognize

Re: arping stuck with ENOBUFS in 4.19.150

2020-10-30 Thread Yunsheng Lin
On 2020/10/30 19:50, Joakim Tjernlund wrote: > On Fri, 2020-10-30 at 09:36 +0800, Yunsheng Lin wrote: >> CAUTION: This email originated from outside of the organization. Do not >> click links or open attachments unless you recognize the sender and know the >> content is safe. >> >> >> On 2020/10/

Re: arping stuck with ENOBUFS in 4.19.150

2020-10-30 Thread Joakim Tjernlund
On Fri, 2020-10-30 at 09:36 +0800, Yunsheng Lin wrote: > CAUTION: This email originated from outside of the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > > On 2020/10/29 23:18, David Ahern wrote: > > On 10/29/20 8:10 A

Re: arping stuck with ENOBUFS in 4.19.150

2020-10-29 Thread Yunsheng Lin
On 2020/10/29 23:18, David Ahern wrote: > On 10/29/20 8:10 AM, Joakim Tjernlund wrote: >> OK, bisecting (was a bit of a bother since we merge upstream releases into >> our tree, is there a way to just bisect that?) >> >> Result was commit "net: sch_generic: aviod concurrent reset and enqueue op >

Re: arping stuck with ENOBUFS in 4.19.150

2020-10-29 Thread Cong Wang
On Thu, Oct 29, 2020 at 7:11 AM Joakim Tjernlund wrote: > > OK, bisecting (was a bit of a bother since we merge upstream releases into > our tree, is there a way to just bisect that?) > > Result was commit "net: sch_generic: aviod concurrent reset and enqueue op > for lockless qdisc" (749cc0b0c

Re: arping stuck with ENOBUFS in 4.19.150

2020-10-29 Thread David Ahern
On 10/29/20 8:10 AM, Joakim Tjernlund wrote: > OK, bisecting (was a bit of a bother since we merge upstream releases into > our tree, is there a way to just bisect that?) > > Result was commit "net: sch_generic: aviod concurrent reset and enqueue op > for lockless qdisc" (749cc0b0c7f3dcdfe5842f

Re: arping stuck with ENOBUFS in 4.19.150

2020-10-29 Thread Joakim Tjernlund
OK, bisecting (was a bit of a bother since we merge upstream releases into our tree, is there a way to just bisect that?) Result was commit "net: sch_generic: aviod concurrent reset and enqueue op for lockless qdisc" (749cc0b0c7f3dcdfe5842f998c0274e54987384f) Reverting that commit on top of ou

Re: arping stuck with ENOBUFS in 4.19.150

2020-10-26 Thread David Ahern
On 10/26/20 6:58 AM, Joakim Tjernlund wrote: > 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\

Re: arping stuck with ENOBUFS in 4.19.150

2020-10-26 Thread Jakub Kicinski
On Mon, 26 Oct 2020 12:58:16 + Joakim Tjernlund wrote: > 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,

Re: arping stuck with ENOBUFS in 4.19.150

2020-10-26 Thread Joakim Tjernlund
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=0x8

arping stuck with ENOBUFS in 4.19.150

2020-10-22 Thread Joakim Tjernlund
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, }, 20) = -1 ENOBUFS (No buffer space available) and then arping loo