From: Brian Rak <brak@vultr.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Repeatable IPv6 crash in 3.19.0-1
Date: Fri, 27 Feb 2015 21:11:16 -0500 [thread overview]
Message-ID: <54F123C4.2030907@vultr.com> (raw)
In-Reply-To: <1425089025.5130.61.camel@edumazet-glaptop2.roam.corp.google.com>
On 2/27/2015 9:03 PM, Eric Dumazet wrote:
> On Fri, 2015-02-27 at 18:01 -0800, Eric Dumazet wrote:
>> On Fri, 2015-02-27 at 20:54 -0500, Brian Rak wrote:
>>
>>> Wow, that was *much* faster then I was expecting, thanks a bunch!
>>>
>>> I can confirm that resolves the issue.. I've tested this and it fixes
>>> the issue perfectly. I've been able to put a whole bunch of IPv6
>>> traffic through the interface now, whereas before even a minor amount of
>>> traffic would crash the host.
>>>
>>> Thanks again!
>>
>> Interesting...
>>
>> Had a prior version of linux kernel been fine ?
>
> Or maybe you recently switched on this config option ?
>
> CONFIG_DEBUG_PAGEALLOC=y
>
>
>
We've only recently started using this veth/macvtap combo, so it's
possible this has been around for awhile and we just hadn't noticed.
I don't have any info on older kernels currently. I *think* I've seen
crashes on 3.17.1, but I didn't save any stack traces, so I can't be sure.
CONFIG_DEBUG_PAGEALLOC is not set, and never has been.
next prev parent reply other threads:[~2015-02-28 2:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 21:37 Repeatable IPv6 crash in 3.19.0-1 Brian Rak
2015-02-28 0:48 ` Eric Dumazet
2015-02-28 1:16 ` Eric Dumazet
2015-02-28 1:54 ` Brian Rak
2015-02-28 2:01 ` Eric Dumazet
2015-02-28 2:03 ` Eric Dumazet
2015-02-28 2:11 ` Brian Rak [this message]
2015-02-28 2:21 ` Eric Dumazet
2015-02-28 2:35 ` [PATCH net] macvtap: make sure neighbour code can push ethernet header Eric Dumazet
2015-03-01 5:30 ` David Miller
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=54F123C4.2030907@vultr.com \
--to=brak@vultr.com \
--cc=eric.dumazet@gmail.com \
--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 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.