netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <erdnetdev@gmail.com>
To: Andrew <nitr0@seti.kr.ua>, Netdev <netdev@vger.kernel.org>
Subject: Re: Kernel panic in eth_header
Date: Tue, 5 Feb 2019 12:28:42 -0800	[thread overview]
Message-ID: <7c2280ea-27dc-667f-78b4-e7eaaf97d337@gmail.com> (raw)
In-Reply-To: <189be8e7-7126-06bf-67bf-53d56ea0723c@seti.kr.ua>



On 02/05/2019 12:21 PM, Andrew wrote:

> I think that backport will be trivial - at least patch lays smoothly on 4.9 (just with offsets difference).
> 
> I'll test it.
> 
> Btw, maybe there's a some test conditions to quickly check if patch helps? Crash is reproducible with unpredictable interval (tens of hours of quite heavy load).
>

Build your kernel with CONFIG_KASAN=y

Then run the tests Peter wrote.

4c3510483d26420d2c2c7cc075ad872286cc5932 selftests: net: ip_defrag: cover new IPv6 defrag behavior
3271a4821882a64214acc1bd7b173900ec70c9bf selftests: net: fix/improve ip_defrag selftest
bccc17118bcf3c62c947361d51760334f6602f43 selftests/net: add ipv6 tests to ip_defrag selftest
02c7f38b7ace9f1b2ddb7a88139127eef4cf8706 selftests/net: add ip_defrag selftest



  reply	other threads:[~2019-02-05 20:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 16:29 Kernel panic in eth_header Andrew
2019-02-05 16:57 ` Eric Dumazet
2019-02-05 19:34   ` Florian Fainelli
2019-02-05 20:13     ` Eric Dumazet
2019-02-05 19:34   ` Florian Fainelli
2019-02-05 20:21     ` Andrew
2019-02-05 20:28       ` Eric Dumazet [this message]
2019-02-05 23:09         ` Andrew
  -- strict thread matches above, loose matches on Subject: below --
2019-02-05 16: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=7c2280ea-27dc-667f-78b4-e7eaaf97d337@gmail.com \
    --to=erdnetdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).