DragonFly BSD
DragonFly bugs List (threaded) for 2005-01
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: (analysis) Re: ipv6 causing panic?

From: Peter Avalos <pavalos@xxxxxxxxxxxx>
Date: Mon, 31 Jan 2005 10:33:05 -0700
Mail-followup-to: bugs@crater.dragonflybsd.org

On Mon, Jan 31, 2005 at 08:42:53AM -0800, Matthew Dillon wrote:
> :I've updated to the latest current sources, and when I bring up
> :my default ipv6 route I get a panic a few seconds later.  Kernel
> :and crash dump can be found at:
> :
> : http://www.theshell.com/~pavalos/crash/
>     It looks like it is IPV6 related.  It crashed somewhere in 
>     in6ifa_ifpwithaddr().
>     Peter, On January 19th I did make a commit which synchronized the
>     use of the interface pointer with consumers when an ifp is freed.
>     Synchronize your sources and make doubly sure that your kernel has
>     those fixes:
>   1.25      +7 -2      src/sys/net/if.c
>   1.23      +78 -3     src/sys/net/netisr.c
>   1.21      +2 -1      src/sys/net/netisr.h
>   1.30      +2 -2      src/sys/netinet/ip_demux.c

Yes, I have all of those.  I used sources from 1/24.

>     From what I can tell, the packet's interface pointer is pointing
>     to memory which is no longer an interface structure.  It's possible
>     that my fixes aren't sufficient for IPV6.  Hmm.  or for packet fragment
>     processing either, since a message may bounce around more then one 
>     thread.  But I am a bit at a loss as to why the interface pointer is
>     bad because you weren't bringing down an interface at the time of the
>     crash (were you?)

No, I was adding a default route.  More specifically, I created a gif
interface, setup a tunnel, gave it an ip, then added a default route.  Once
I added the default route, it would crash.

I'm going to update to the latest sources, kill /usr/obj, and try again.


[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]