Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 4 Sep 2002 14:18:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 4 Sep 2002 14:18:38 -0400 Received: from [195.223.140.120] ([195.223.140.120]:23656 "EHLO penguin.e-mind.com") by vger.kernel.org with ESMTP id ; Wed, 4 Sep 2002 14:18:37 -0400 Date: Wed, 4 Sep 2002 20:22:23 +0200 From: Andrea Arcangeli To: lists@corewars.org Cc: riel@conectiva.com.br, marcelo@conectiva.com.br, linux-kernel@vger.kernel.org Subject: Re: 2.4.19 OOPS [Repost] Message-ID: <20020904182223.GE1210@dualathlon.random> References: <20020903190726.A15065@corewars.org> <20020904201155.A17544@corewars.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020904201155.A17544@corewars.org> User-Agent: Mutt/1.3.27i X-GnuPG-Key-URL: http://e-mind.com/~andrea/aa.gnupg.asc X-PGP-Key-URL: http://e-mind.com/~andrea/aa.asc Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 885 Lines: 20 On Wed, Sep 04, 2002 at 08:11:55PM +0200, lists@corewars.org wrote: > Just in case this had someone wondering, the problem was swap > corruption. I did an mkswap on the swap partition, and it doesn't > OOPS anymore. make sense. The reason of the corruption could be from hardware fault to whatever buggy application that played with the devices, so unless you can reproduce I'd ignore this on the kernel side, at least on 2.4 (kernel trusts metadata, the fs does too, kernel assumes if the data is corrupted an I/O error has to be generated by the hardware, we can add some check to make it more robust but it's not a 2.4 matter). Andrea - 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/