[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpWOhXR=x10i0S88qXTfG2nv9EypONTp6_vpBzs=iOySRQ@mail.gmail.com>
Date: Thu, 19 Dec 2019 12:50:14 -0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Yoshiki Komachi <komachi.yoshiki@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jamal Hadi Salim <jhs@...atatu.com>,
Jiri Pirko <jiri@...nulli.us>,
Amritha Nambiar <amritha.nambiar@...el.com>,
netdev <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: refcount_warn_saturate WARNING (was: Re: cls_flower: Fix the
behavior using port ranges with hw-offload)
On Thu, Dec 19, 2019 at 2:12 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> I still see the below warning on m68k/ARAnyM during boot with v5.5-rc2
> and next-20191219.
> Reverting commit 8ffb055beae58574 ("cls_flower: Fix the behavior using
> port ranges with hw-offload") fixes that.
>
> As this is networking, perhaps this is seen on big-endian only?
> Or !CONFIG_SMP?
>
> Do you have a clue?
> I'm especially worried as this commit is already being backported to stable.
> Thanks!
I did a quick look at the offending commit, I can't even connect it to
any dst refcnt.
Do you have any more information? Like what happened before the
warning? Does your system use cls_flower filters at all? If so, please
share your tc configurations.
Thanks.
Powered by blists - more mailing lists