This is a discussion on Re: ipfw: LOR/panic with uid rules - FreeBSD ; On Thursday 25 September 2008 00:45:17 Robert Watson wrote: > On Thu, 25 Sep 2008, Stefan Ehmann wrote: > >> Hmm. Is it identical, or a different stack trace? Could you tell me what > >> $FreeBSD$ appears in your ...
On Thursday 25 September 2008 00:45:17 Robert Watson wrote:
> On Thu, 25 Sep 2008, Stefan Ehmann wrote:
> >> Hmm. Is it identical, or a different stack trace? Could you tell me what
> >> $FreeBSD$ appears in your tcp_input.c? (I've committed the patch since
> >> it's definitely necessary, even if it doesn't fix the specific instance
> >> of the problem you're seeing).
> > I cvsup-ed and noticed the patch is already committed. I double-checked
> > after the problem was still there.
> > The LORs seem identical. The panic backtrace is slightly different
> > (besides the double panic):
> None of the line numbers in this trace seem to line up with expected things
> in the source code. Could you confirm your source code, vmcore, and kernel
> are all in sync? Could you also confirm for me what version of tcp_input.c
> you're using?
Hmm, just obtained a new dump which was the same. Did a normal "make kernel",
so source/kernel should be in sync
This is the version:
__FBSDID("$FreeBSD: src/sys/netinet/tcp_input.c,v 1.382 2008/09/24 11:07:03
rwatson Exp $");
What doesn't match? I only checked this and it looks okay to me
> > #26 0xc0943d95 in tcp_respond (tp=0x0, ipgen=0xc4dde016, th=0xc4dde02a,
> > m=0xc4db8600, ack=0, seq=1465052506, flags=Variable "flags" is not
> > available.
> > )
> > at /usr/src/sys/netinet/tcp_subr.c:611
> > #27 0xc093a955 in tcp_dropwithreset (m=0xc4db8600, th=0xc4dde02a, tp=0x0,
> > tlen=1440, rstreason=3) at /usr/src/sys/netinet/tcp_input.c:2552
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "email@example.com"