[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpX8=wege1toTsWpKHFMVAzM90HLQ51nzsn0LrDW=CEhiA@mail.gmail.com>
Date: Thu, 29 Oct 2020 12:10:33 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
Cc: "dsahern@...il.com" <dsahern@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"kuba@...nel.org" <kuba@...nel.org>
Subject: Re: arping stuck with ENOBUFS in 4.19.150
On Thu, Oct 29, 2020 at 7:11 AM Joakim Tjernlund
<Joakim.Tjernlund@...inera.com> 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?
This is odd. The above commit touches the netdev reset path, did
your netdev get reset when you ran arping? You said your eth1 is UP,
is it always UP or flapping?
In the other thread, a bisect also points to the same commit on 5.4.
I guess there might be something missing in the backport.
Thanks.
Powered by blists - more mailing lists