Re: odd memory corruption in 2.5.27?

[Trond Myklebust]

On Tuesday 23 July 2002 08:26, Zwane Mwaikambo wrote:
> Hi Trond, Arnaldo, Al
> 	I tried reproducing using a local filesystem and couldn't
> (machine survived 3 make -j10 kernel compiles). Here is another oops for
> the collection. Al i'll remove you from further CCs now.
>
> client: 2.5.27-serial, 3c905B
> server: 2.4.19-pre5-ac3, 3c905B
> connection: 100Mb/FD
>
> I got this message before it oopsed;
> RPC: garbage, exit EIO

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).

Cheers,
  Trond