Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Nov 2003 23:28:07 +0100
From:      Andre Oppermann <oppermann@pipeline.ch>
To:        Hajimu UMEMOTO <ume@mahoroba.org>
Cc:        sam@errno.com
Subject:   Re: tcp hostcache and ip fastforward for review
Message-ID:  <3FB16277.9E658A8E@pipeline.ch>
References:  <3FAE68FB.64D262FF@pipeline.ch> <ygey8um974u.wl%ume@mahoroba.org> <3FB129E1.5D8F4D16@pipeline.ch> <ygellqmekws.wl%ume@mahoroba.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hajimu UMEMOTO wrote:
> 
> Hi,
> 
> >>>>> On Tue, 11 Nov 2003 19:26:41 +0100
> >>>>> Andre Oppermann <oppermann@pipeline.ch> said:
> 
> oppermann> I have fixed the panic. It was a stupid braino in the test whether
> oppermann> we have to free the allocated route. It was trying to free a null
> oppermann> pointer route which obviously doesn't work. :-^
> 
> oppermann> The updated patch is here:
> 
> oppermann>  http://www.nrg4u.com/freebsd/tcphostcache+ipfastforward-20031111.patch
> 
> oppermann> If you could try again please?
> 
> It panics at another point on boot.
> (kgdb) frame 24
> #24 0xc058e637 in tcp_hc_getmtu (inc=0x0)
>     at /usr/home/ume/cvs/freefall/current/src/sys/netinet/tcp_hostcache.c:420
> 420             hc_entry = tcp_hc_lookup(inc);
> (kgdb)

Did the panic message say "tcp_hc_lookup with NULL in_conninfo pointer"?

I can't find why inc can be possibly NULL because its fresh and directly
on the stack.

But I'm too tired right now (that's probably why I don't see atm).
Next try tomorrow morning (mid-European time).

-- 
Andre



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FB16277.9E658A8E>