I speculate that the problem you are seeing in netinet6 is due to it not
freeing referenced in6_multi objects when the interface address changes
or the same address is re-added, as the same bug was present in netinet.
Previous to the introduction of refcounting, FreeBSD would just leak memory.
Andrew Thompson wrote:
I have come across this panic which appears to be from incorrect
refcounting on the inet6 multicast code.
I can reproduce this panic, however I don't entirely understand what's
going on. When the same IPv6 unicast address is configured twice on the
edsc0 interface, t
On Thu, Apr 12, 2007 at 09:43:44AM +0100, Bruce M. Simpson wrote:
> Andrew Thompson wrote:
> >I have come across this panic which appears to be from incorrect
> >refcounting on the inet6 multicast code.
> >
> I'm assuming this is in -CURRENT, as the refcount code has not yet been
> MFCed.
Yes
Andrew Thompson wrote:
I have come across this panic which appears to be from incorrect
refcounting on the inet6 multicast code.
I'm assuming this is in -CURRENT, as the refcount code has not yet been
MFCed.
...
in6m_refcount is still 1 so the in6_multi is not freed.
I'll try to investi
Hi,
I have come across this panic which appears to be from incorrect
refcounting on the inet6 multicast code.
[EMAIL PROTECTED] ifconfig edsc0 create
[EMAIL PROTECTED] ifconfig edsc0 inet6 f00f::01
[EMAIL PROTECTED] ifconfig edsc0 destroy
Everything is ok...
[EMAIL PROTECTED] ifconfig edsc0 cr
