From: Alexander Duyck <alexander.duyck@gmail.com>
To: Andrew <nitr0@seti.kr.ua>, netdev@vger.kernel.org
Subject: Re: Kernel 4.1.12 crash
Date: Fri, 20 Nov 2015 15:13:08 -0800 [thread overview]
Message-ID: <564FA904.7020603@gmail.com> (raw)
In-Reply-To: <564F26FF.3040605@seti.kr.ua>
On 11/20/2015 05:58 AM, Andrew wrote:
> Hi all.
>
> Today some BRASes on 4.1.12 kernel were crashed.
>
> Here's crash traces: http://pastebin.com/p68hNS8R
> http://pastebin.com/36ieRAM2 http://pastebin.com/3BRTVEB6
>
> On 3.2 kernel same hardware works OK, troubles were noticed after kernel
> upgrade.
>
> What additional info is needed?
Looking over the traces there seem to be two areas called out.
The first is the fib_trie resize BUG_ON that was triggered due to the
parent and child not being associated. I think that might be due to
memory corruption as I cannot find any spots where we are resizing
without correctly setting up the parent-child relationship of the nodes
first.
The other spot that is showing up is ppp_shutdown_interface and it's
related path. It looks like there are a couple of patches you could try
back-porting to see if it resolves the issue. If they do then perhaps
they should be considered candidates for stable:
8cb775bc0a3 ("ppp: fix device unregistration upon netns deletion")
58a89ecaca5 ("ppp: fix lockdep splat in ppp_dev_uninit()")
- Alex
next prev parent reply other threads:[~2015-11-20 23:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 13:58 Kernel 4.1.12 crash Andrew
2015-11-20 23:13 ` Alexander Duyck [this message]
2015-11-21 8:16 ` Andrew
2015-11-22 5:17 ` Alexander Duyck
2015-11-22 10:45 ` Andrew
2015-11-24 22:59 ` Andrew
2015-11-25 9:35 ` Andrew
2015-11-25 14:10 ` Guillaume Nault
[not found] ` <5655CCAE.6000300@seti.kr.ua>
2015-11-26 16:44 ` Guillaume Nault
[not found] ` <565B7699.8030105@seti.kr.ua>
2015-11-30 15:03 ` Guillaume Nault
2015-11-30 20:42 ` Guillaume Nault
2015-12-02 17:23 ` Guillaume Nault
2015-12-03 15:35 ` Guillaume Nault
2015-12-03 21:09 ` Andrew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=564FA904.7020603@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nitr0@seti.kr.ua \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.