netdev - Re: arping stuck with ENOBUFS in 4.19.150

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 29 Oct 2020 09:18:41 -0600
From:   David Ahern <dsahern@...il.com>
To:     Joakim Tjernlund <Joakim.Tjernlund@...inera.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "kuba@...nel.org" <kuba@...nel.org>,
        Yunsheng Lin <linyunsheng@...wei.com>
Subject: Re: arping stuck with ENOBUFS in 4.19.150

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"  (749cc0b0c7f3dcdfe5842f998c0274e54987384f)
> 
> Reverting that commit on top of our tree made it work again. How to fix?

Adding the author of that patch (linyunsheng@...wei.com) to take a look.


> 
>  Jocke
>  
> On Mon, 2020-10-26 at 12:31 -0600, David Ahern wrote:
>>
>> 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\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
>>>
>>
>> do a git bisect between the releases to find out which commit is causing
>> the change in behavior.
>