netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yunsheng Lin <linyunsheng@huawei.com>
To: David Ahern <dsahern@gmail.com>,
	Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: arping stuck with ENOBUFS in 4.19.150
Date: Fri, 30 Oct 2020 09:36:34 +0800	[thread overview]
Message-ID: <4641f25f-7e7f-5d06-7e00-e1716cbdeddc@huawei.com> (raw)
In-Reply-To: <bf33dfc1-8e37-8ac0-7dcb-09002faadc7a@gmail.com>

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 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@huawei.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.

"eth1 is UP but not RUNNING" usually mean user has configure the netdev as up,
but the hardware has not detected a linkup yet.

Also What is the output of "ethtool eth1"?

It would be good to see the status of netdev before and after executing arping cmd
too.

Thanks.

>>>>>
>>>>>  Jocke
>>>>
>>>
>>> do a git bisect between the releases to find out which commit is causing
>>> the change in behavior.

unfortunately, I did not reproduce the above problem in 4.19.150 too.

root@(none)$ arping -q -c 1 -b -U  -I eth0 0.0.0.0
root@(none)$ arping -v
ARPing 2.21, by Thomas Habets <thomas@habets.se>
usage: arping [ -0aAbdDeFpPqrRuUv ] [ -w <sec> ] [ -W <sec> ] [ -S <host/ip> ]
              [ -T <host/ip ] [ -s <MAC> ] [ -t <MAC> ] [ -c <count> ]
              [ -C <count> ] [ -i <interface> ] [ -m <type> ] [ -g <group> ]
              [ -V <vlan> ] [ -Q <priority> ] <host/ip/MAC | -B>
For complete usage info, use --help or check the manpage.
root@(none)$ cat /proc/version
Linux version 4.19.150 (linyunsheng@ubuntu) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.12)) #4 SMP PREEMPT Fri Oct 30 09:22:06 CST 2020



>>
> 
> 

  reply	other threads:[~2020-10-30  1:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 15:19 arping stuck with ENOBUFS in 4.19.150 Joakim Tjernlund
2020-10-26 12:58 ` Joakim Tjernlund
2020-10-26 16:27   ` Jakub Kicinski
2020-10-26 18:31   ` David Ahern
2020-10-29 14:10     ` Joakim Tjernlund
2020-10-29 15:18       ` David Ahern
2020-10-30  1:36         ` Yunsheng Lin [this message]
2020-10-30 11:50           ` Joakim Tjernlund
2020-10-31  1:48             ` Yunsheng Lin
2020-11-02  8:27               ` Joakim Tjernlund
2020-10-29 19:10       ` Cong Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4641f25f-7e7f-5d06-7e00-e1716cbdeddc@huawei.com \
    --to=linyunsheng@huawei.com \
    --cc=Joakim.Tjernlund@infinera.com \
    --cc=dsahern@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).