Subject: Re: packet filtering bug and a question
To: None <firstname.lastname@example.org>
From: Tom Spindler <email@example.com>
Date: 10/30/1999 15:38:17
> > Heh. I wonder if the code correctly deals with the situation if
> > DIAGNOSTIC is turned off.... Also, during my playing with the filters, I
> > got a message that said something about a value in freelist being changed,
> > with previous value 0xdeadbeef. Anyway, there's something lurking there,
> > too, I think.
> Quite probably. The 'value in freelist being changed' is not good, for
> sure. That function, though, would simply exit if DIAGNOSTIC was not
> defined. I don't think it's supposed to even get to that function if
> there's nothing to remove.
I believe this bug was just discussed on tech-kern; IIRC, it's related
to an fd not being freed in some correct manner, and there was a tenative