Re: odd memory corruption in 2.5.27?

From: Zwane Mwaikambo (zwane@linuxpower.ca)
Date: Tue Jul 23 2002 - 03:54:24 EST

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/

This archive was generated by hypermail 2b29 : Tue Jul 23 2002 - 22:00:42 EST