[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADuNpCyv=nh8iMrRp=T1qqi3j6pfZJyfqKagqDtAo6+ux-b1xg@mail.gmail.com>
Date: Wed, 30 Jan 2019 12:28:10 -0500
From: Lance Richardson <lance604@...il.com>
To: Cong Wang <xiyou.wangcong@...il.com>
Cc: Ivan Babrou <ivan@...udflare.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Ignat Korchagin <ignat@...udflare.com>,
Shawn Bohrer <sbohrer@...udflare.com>,
Jakub Sitnicki <jakub@...udflare.com>
Subject: Re: Crashes in skb clone/allocation in 4.19.18
On Wed, Jan 30, 2019 at 12:17 PM Cong Wang <xiyou.wangcong@...il.com> wrote:
>
> On Wed, Jan 30, 2019 at 8:54 AM Ivan Babrou <ivan@...udflare.com> wrote:
> >
> > Hey,
> >
> > We've upgraded some machines from 4.19.13 to 4.19.18 and some of them
> > crashed with the following:
> >
> > [ 2313.192006] general protection fault: 0000 [#1] SMP PTI
> > [ 2313.205924] CPU: 32 PID: 65437 Comm: nginx-fl Tainted: G
> > O 4.19.18-cloudflare-2019.1.8 #2019.1.8
"Tainted: GO" appears to mean that an out-of tree kernel module was
loaded. If so, information about that module and whether the crash
occurs when it hasn't been loaded might be of interest.
- Lance
> > [ 2313.224973] Hardware name: Quanta Computer Inc. QuantaPlex
> > T41S-2U/S2S-MB, BIOS S2S_3B10.03 06/21/2018
> > [ 2313.243400] RIP: 0010:kmem_cache_alloc_node+0x178/0x1f0
>
> This looks more like an mm bug than a networking one.
>
> Also, it is always helpful if you can map the RIP to source code,
> using scripts/faddr2line or scripts/decode_stacktrace.sh.
>
>
> Thanks.
>
Powered by blists - more mailing lists