[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb4c7049-9f5a-6f2b-840f-3eb42b9307f5@gmail.com>
Date: Wed, 6 Feb 2019 17:50:03 -0800
From: David Ahern <dsahern@...il.com>
To: Ben Greear <greearb@...delatech.com>,
netdev <netdev@...r.kernel.org>
Subject: Re: Waiting for vrf to become free on rmmod of bridge...
On 2/6/19 3:20 PM, Ben Greear wrote:
> Hello,
>
> I just saw this warning on a system running a hacked 4.20.2+ kernel.
> Any known bugs
> of this nature in this (upstream) kernel? The command that is blocked is:
> 'rmmod bridge llc'
>
> [17069.299135] unregister_netdevice: waiting for _vrf13 to become free.
> Usage count = 1
> [17079.306438] unregister_netdevice: waiting for _vrf13 to become free.
> Usage count = 1
> [17089.314656] unregister_netdevice: waiting for _vrf13 to become free.
> Usage count = 1
> [17099.322870] unregister_netdevice: waiting for _vrf13 to become free.
> Usage count = 1
>
> Thanks,
> Ben
>
No known refcount issues with vrf.
I use namespaces for testing which creates devices, adds routes, runs
traffic and deletes the device and namespace. That series in the tests
has been known to trigger refcount problems in the past.
Powered by blists - more mailing lists