[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <0231E33E-1C1A-4B32-992C-9BFC7470E7E0@cumulusnetworks.com>
Date: Wed, 8 Jun 2016 22:35:52 -0600
From: David Ahern <dsa@...ulusnetworks.com>
To: Eric Dumazet <edumazet@...gle.com>
Cc: "David S . Miller" <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: [PATCH v2 net-next 2/4] net: vrf: call netdev_lockdep_set_classes()
> On Jun 8, 2016, at 10:01 PM, Eric Dumazet <edumazet@...gle.com> wrote:
>
>> On Wed, Jun 8, 2016 at 8:41 PM, David Ahern <dsa@...ulusnetworks.com> wrote:
>>> On 6/8/16 9:29 PM, Eric Dumazet wrote:
>>>
>>> In case a qdisc is used on a vrf device, we need to use different
>>> lockdep classes to avoid false positives.
>>>
>>> Fixes: f9eb8aea2a1e ("net_sched: transform qdisc running bit into a
>>> seqcount")
>>> Reported-by: David Ahern <dsa@...ulusnetworks.com>
>>> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
>>
>>
>> same result with this patch set.
>
> Are you stacking multiple vrf devices ?
No. You can also look at ipvlan. It shows the same trace. For me it is 3 commands that create the vrf, add eth1, run ping.
Powered by blists - more mailing lists