> > When I built IPv6 as a module under 2.1.63, inserted the module and
> > removed it, here's what I got:
>
> "Doctor! When I do this [...], it hurts!"
> "Well, don't do it then!"
>
> Seriously, yes, we know "rmmod ipv6" is bad for your system health.
> The interesting thing is, which object if being freed (twice ?)
> Do "ksyms -a > /tmp/running.symbols" before trying "rmmod"
> anything.
It fails in ipv6/addrconf.c:addrconf_cleanup() in the "clean dev list"
loop. I didn't get around to debug it yet (found so many other showstopper
bugs in ipv6 that have priority). But it's interesting information that
it happens in stock 2.1.63 too, I would have guessed that it was caused
by Alexey's changes in the VGER tree. I'll look into it.
-A.