From: Eric Dumazet <eric.dumazet@gmail.com>
To: Frank Wunderlich <frank-w@public-files.de>, netdev@vger.kernel.org
Subject: Re: [BUG] kernel panic 4.14.95 in kmem_cache_alloc / build_skb
Date: Wed, 6 Feb 2019 10:48:13 -0800 [thread overview]
Message-ID: <418df4d9-1f32-b7cd-f903-ff29751e3a22@gmail.com> (raw)
In-Reply-To: <trinity-9b22aadc-4955-4b89-8975-e7497ee92f4c-1549474599369@3c-app-gmx-bs23>
On 02/06/2019 09:36 AM, Frank Wunderlich wrote:
> Hi,
>
> linux-net-mailinglist for reporting bugs seems not existing anymore and i have not found out the right one..."scripts/get_maintainer.pl -f ./include/linux/skbuff.h" shows only linux-kernel as mailing list which is not specific for network, so sorry, if i'm in the wrong mailinglist.
>
> i've recently noticed panics on my bananapi-r2 with kernel 4.14.95, but can't locate them in detail...all is pointing to kmem_cache_alloc and build_skb, but over complete different ways. so i guess it's network-related
>
> i currently don't know what is triggering this crashes, so i cannot reproduce them on my test-machine :(
>
> it's not only an oops...the machine stays still and have to be resettet, sometimes after an half hour running
>
> i had kernel 4.14.78 running before, so i think it's a change between these 2 Kernel-versions and no OS-related (debian-stretch) or Hardware-issue
>
> currently i test with 4.14.90, if it has same behaviour...at the moment it seems stable...
>
> i cannot test it with another kernel-branch (4.19+), because i need to test it on my productive machine till i find a way to reproduce it....maybe you can see a hint in stacktrace to guide me...at the moment crash occours unexpectely
>
> i looked through git-tree but did not found anything related
>
> regards Frank
>
> here my 3 recorded crash-logs...maybe you can point me in the right direction (reproduce/debug/fix):
Make sure to try 4.14.98, as I am guessing this has been fixed by :
dc489ad6a2f2fcebdaecb7b8532e0d02d272ac6a Fix "net: ipv4: do not handle duplicate fragments as overlapping"
next prev parent reply other threads:[~2019-02-06 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 17:36 [BUG] kernel panic 4.14.95 in kmem_cache_alloc / build_skb Frank Wunderlich
2019-02-06 18:48 ` Eric Dumazet [this message]
2019-02-07 8:32 ` Aw: " Frank Wunderlich
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=418df4d9-1f32-b7cd-f903-ff29751e3a22@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=frank-w@public-files.de \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox