[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190322033609.fvoz3tulgzrjdhwm@ast-mbp.dhcp.thefacebook.com>
Date: Thu, 21 Mar 2019 20:36:11 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...com>,
Networking <netdev@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>
Subject: Re: [BUG] BPF splat on latest kernels
On Wed, Mar 20, 2019 at 09:49:34PM -0700, Eric Dumazet wrote:
>
>
> On 03/08/2019 04:29 PM, Alexei Starovoitov wrote:
> > On Fri, Mar 8, 2019 at 12:33 PM Eric Dumazet <eric.dumazet@...il.com> wrote:
> >>
> >> Running test_progs on a LOCKDEP enabled kernel (latest David Miller net tree)
> >>
> >> I got the following splat.
> >>
> >> It is not immediately obvious to me. Any idea ?
> >
> > I think I saw something similar running test_maps,
> > but I had other changes in the tree. And later I was
> > never able to reproduce it, so figured it must have
> > been my local change. Looks like it was for real.
> > Do you have a reproducer?
> > I'll take a look on monday.
>
> Hi Alexei
>
> Has this problem been root caused ?
This is not forgotten.
I'm prioritizing bpf code reviews at the moment since backlog is still big
and developers are waiting.
If somebody can dig into this lockdep splat it would be great.
Powered by blists - more mailing lists