Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 5 Feb 2001 11:58:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 5 Feb 2001 11:58:06 -0500 Received: from orange.csi.cam.ac.uk ([131.111.8.77]:44702 "EHLO orange.csi.cam.ac.uk") by vger.kernel.org with ESMTP id ; Mon, 5 Feb 2001 11:58:01 -0500 Date: Mon, 5 Feb 2001 16:57:21 +0000 (GMT) From: James Sutherland To: Hans Reiser cc: Alan Cox , "Albert D. Cahalan" , Brian Wolfe , Ion Badulescu , linux-kernel@vger.kernel.org, reiserfs-list@namesys.com, Jan Kasprzak Subject: Re: [reiserfs-list] ReiserFS Oops (2.4.1, deterministic, symlink related) In-Reply-To: <3A7E904F.797AF09B@namesys.com> 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 On Mon, 5 Feb 2001, Hans Reiser wrote: > Alan Cox wrote: > > > > > In an __init function, have some code that will trigger the bug. > > > This can be used to disable Reiserfs if the compiler was bad. > > > Then the admin gets a printk() and the Reiserfs mount fails. > > > > Thats actually quite doable. I'll see about dropping the test into -ac that > > way. > NOOOOO!!!!!! It should NOT fail at mount time, it should fail at compile time. A simple "make test" to run this sort of automated sanity check would be good, I think? James. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/