Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 23 Jul 2002 04:33:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 23 Jul 2002 04:33:27 -0400 Received: from [196.26.86.1] ([196.26.86.1]:33686 "HELO infosat-gw.realnet.co.sz") by vger.kernel.org with SMTP id ; Tue, 23 Jul 2002 04:33:27 -0400 Date: Tue, 23 Jul 2002 10:54:24 +0200 (SAST) From: Zwane Mwaikambo X-X-Sender: zwane@linux-box.realnet.co.sz To: Trond Myklebust Cc: Linux Kernel Subject: Re: odd memory corruption in 2.5.27? In-Reply-To: <200207230957.19812.trond.myklebust@fys.uio.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 989 Lines: 27 On Tue, 23 Jul 2002, Trond Myklebust wrote: > Just means that some RPC message reply from the server was crap. We should > deal fine with that sort of thing... > > AFAICS The Oops itself happened deep down in the socket layer in the part > which has to do with reassembling fragments into packets. The garbage > collector tried to release a fragment that had timed out and Oopsed. > > Suggests either memory corruption or else that the networking driver is doing > something odd ('cos at that point in the socket layer *only* the driver + the > fragment handler should have touched the skb). Thanks, that helps quite a bit, i'll see if i can pinpoint it and send it to the relevant people. Thanks, Zwane -- function.linuxpower.ca - 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/