Squid-2.5.STABLE5 still not ready

The Squid-2.5.STABLE5 release is unfortunately still not ready. Being
blocked by Bug #891 <http://www.squid-cache.org/bugs/show_bug.cgi?id=891>

This bug report covers two symptoms, both indicating that somehow an
ipcache entry gets freed while it is still active.

A) Segfault due to NULL pointer referencing an entry which is cleared
(freed)

B) 100% CPU loop due to a cyclic ipcache LRU list. My guess is that this
is probably caused by the ipcache entry previously freed is now reused and
inserted into the list before triggering problem 'A' above.

I have been staring at the ipcache code but can for my life not figure out
what may go wrong causing such symptoms. Can I please get a few other eyes
looking into this problem?

To make things even more strange this problem apparently is introduced
some time in November, but there has not been any ipcache or dlink related
changes from what I can see..

Regards
Henrik
Received on Wed Feb 11 2004 - 15:29:43 MST