content-class: urn:content-classes:message
Subject: route cache corruption
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Date: Sun, 14 Jul 2002 13:53:42 +0200
Message-ID: <4913AB320D31DC4798D6FEF5F557351F159764@hawk.exanet-il.co.il>
Thread-Topic: route cache corruption
Thread-Index: AcIrLXARz1NF+NukR0ObSwzTUTvkmA==
From: "Nir Soffer" <nirs@exanet.com>
To: <kuznet@ms2.inr.ac.ru>
Cc: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1225
Lines: 35


Hi!

We've been having some problems with the route cache corrupting on us,
suddenly every connection we made went out to the loopback interface,
and right back in the machine.

I've seen a patch in the 2.4.19 changelog headline:
"        Terrible bug in ipv4/route.c, mis-sized ip_rt_acct leads to"

Could this be the cause of this phenomena, or am I barking up the
wrong tree?

I'm currently running a modified 2.4.18-4. I'm aware that straying
from the vanilla is a recipe for trouble - but I'm wondering if this
specific problem could be caused by this bug. I haven't found anything
in the archives telling me what exactly this bug does. All I've seen
are references to it.

Thanks for any help you can give me!

Nir.


--
Nir Soffer -=- Software Engineer, Exanet Inc. -=-
"Father, why are all the children weeping? / They are merely crying son
 O, are they merely crying, father? / Yes, true weeping is yet to come"
        -- Nick Cave and the Bad Seeds, The Weeping Song
 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/