[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+G9fYvEK4F8PbvjeRK3+6WeEFXExQpQ3MS2CE2gD6phV+Q5dg@mail.gmail.com>
Date: Tue, 18 Jun 2019 13:09:40 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: Hillf Danton <hdanton@...a.com>
Cc: Netdev <netdev@...r.kernel.org>,
linux- stable <stable@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>, sgarzare@...hat.com,
Daniel Borkmann <daniel@...earbox.net>, kafai@...com,
jakub@...udflare.com, lkft-triage@...ts.linaro.org,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>, john.fastabend@...il.com
Subject: Re: kernel/workqueue.c:3030 __flush_work+0x2c2/0x2d0
Hi Hillf,
On Tue, 18 Jun 2019 at 09:40, Hillf Danton <hdanton@...a.com> wrote:
>
>
> Hello
>
> On Sun, 16 Jun 2019 19:30:27 -0700 (PDT) Naresh Kamboju wrote:
> > Kernel warning while running kernel selftest bpf test_sockmap test case on
> > x86_64 and arm64.
> > The kernel warning log pops up continuously.
> >
> > Linux version 5.1.10-rc2
> >
> > Steps to reproduce:
> > Boot stable rc 5.1.10-rc2 kernel on x86_64 or arm64
> > cd selftests/bpf
> > ./test_sockmap
> >
> > [ 37.600406] WARNING: CPU: 3 PID: 57 at /usr/src/kernel/kernel/workqueue.c:3030 __flush_work+0x2c2/0x2d0
...
> >
> >
> Only find this; wish it may be paving a brick perhaps for those looking to fix the
> 3030 warning.
>
>
> Hillf
Thanks for looking into this problem,
There is a recent patch fixed this problem on 5.1.12 stable rc branch today
and AUTOSEL on current stable review.
bpf: sockmap, only stop/flush strp if it was enabled at some point
link: https://lore.kernel.org/lkml/20190604232212.6753-12-sashal@kernel.org/
Best regards
Naresh Kamboju
Powered by blists - more mailing lists