Re: 2.6.7-rc3: unregister_netdevice: waiting for tun0 to become free. Usage count = 1

[Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>]

On Sun, Jun 13, 2004 at 09:27:08PM -0700, David S. Miller wrote:
>
> > 1. The code in dst_dev_event relies on the entries with dev in it
> > getting onto the garbage list before it is called.  Unfortunately
> > for routing entries, the flushing is done asynchronusly so it is
> > entirely possible for the entries to get onto the garbage list after
> > dst_dev_event has been called twice (DOWN and then UNREGISTER).
> > 
> > This is not fatal though since another GC run will pick them up in
> > at most two minutes.  But the user may well be alarmed by those
> > dreaded "waiting for..." errors.
> 
> Right.
> 
> > 2. dst_dev_event doesn't clean up dst->child at all.
> 
> DST object is disassembled at GC time, so I classift this just
> like case #1 above.

Yes.  In fact the loopback_dev code in dst_dev_event is also like
this.  Removing that code will simply defer the dropping of the
dev reference to the GC.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email:  Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt