From: Ben Greear <greearb@candelatech.com>
To: Cong Wang <cwang@twopensource.com>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>,
Hongmei Li <duckcncn@gmail.com>, netdev <netdev@vger.kernel.org>
Subject: Re: IPv6 FIB related crash with MACVLANs in 3.9.11+ kernel.
Date: Mon, 29 Sep 2014 14:24:54 -0700 [thread overview]
Message-ID: <5429CE26.6000108@candelatech.com> (raw)
In-Reply-To: <CAHA+R7O_xghD4a5RD=omhnuMD72pRmKU9VMoxPUVuGcu682jBg@mail.gmail.com>
On 09/29/2014 01:39 PM, Cong Wang wrote:
> On Mon, Sep 29, 2014 at 12:48 PM, Ben Greear <greearb@candelatech.com> wrote:
>>
>> We are going to be running up to 20 concurrent scripts that
>> will be dumping routes & ips, and configuring ip addresses
>> and routes during bringup.
>>
>> I don't have a simple stand-alone way to reproduce this,
>> but at least when we reported the problem is was very easy
>> for us to reproduce with our tool.
>>
>> Maybe 20 scripts running in parallel that randomly configured and dumped routes
>> and ip addresses on random interfaces would do the trick?
>>
>
> I think the most important question is why is this related with macvlan?
> IPv6 is L3 while macvlan pure L2, if this is a IPv6 routing bug, it should
> not be limited to macvlan.
We saw it using mac-vlans on top of ixgbe. Probably it can be reproduced
elsewhere, but since we had a good test case, we didn't bother trying lots
of other combinations.
Just enabling some debug code caused the problem to be much harder
to reproduce, so it is probably some sort of race. Maybe lots of mac-vlans
make it easier to hit.
> What does your IPv6 routing table look like? And how do you configure those
> macvlan interfaces?
Each interface would have it's own routing table, with at least as subnet
route. I'm not sure we were adding a default gateway or not.
The main routing table would also have some auto-created routes
I think.
It is configured using 'ip' to add and dump routes.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-09-29 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 20:37 IPv6 FIB related crash with MACVLANs in 3.9.11+ kernel Ben Greear
2014-02-03 22:03 ` Hannes Frederic Sowa
2014-02-03 22:06 ` Ben Greear
2014-02-08 16:43 ` Ben Greear
2014-02-08 17:23 ` Hannes Frederic Sowa
2014-09-25 22:24 ` Hongmei Li
2014-09-28 12:11 ` Hannes Frederic Sowa
2014-09-29 18:15 ` Hongmei Li
2014-09-29 18:44 ` Ben Greear
2014-09-29 19:03 ` Hannes Frederic Sowa
2014-09-29 19:48 ` Ben Greear
2014-09-29 20:39 ` Cong Wang
2014-09-29 21:24 ` Ben Greear [this message]
2014-10-12 11:42 ` Vladislav Yasevich
2014-10-13 18:06 ` Ben Greear
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=5429CE26.6000108@candelatech.com \
--to=greearb@candelatech.com \
--cc=cwang@twopensource.com \
--cc=duckcncn@gmail.com \
--cc=hannes@stressinduktion.org \
--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;
as well as URLs for NNTP newsgroup(s).