Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 2 Dec 2001 12:00:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 2 Dec 2001 11:59:47 -0500 Received: from leibniz.math.psu.edu ([146.186.130.2]:20160 "EHLO math.psu.edu") by vger.kernel.org with ESMTP id ; Sun, 2 Dec 2001 11:59:38 -0500 Date: Sun, 2 Dec 2001 11:59:34 -0500 (EST) From: Alexander Viro To: Pierre Rousselet cc: Richard Gooch , Marcelo Tosatti , Keith Owens , linux-kernel@vger.kernel.org Subject: Re: 2.5.1-pre5 not easy to boot with devfs In-Reply-To: <3C0A025C.88B7A2C3@wanadoo.fr> 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 Sun, 2 Dec 2001, Pierre Rousselet wrote: > Here is the final (i hope) verdict of my devfs testbox : > > 2.4.16 with devfsd-1.3.18/1.3.20 : OK > 2.4.17-pre1 " : Broken > 2.5.1-pre1 " : OK > 2.5.1-pre2 with or without v200 : Broken > 2.5.1-pre5 " : Broken IOW, merge of new devfs code (2.4.17-pre1 in -STABLE, 2.5.1-pre2 in -CURRENT). We really need CONFIG_DEBUG_* forced if CONFIG_DEVFS_FS is set. Otherwise we'll be getting tons of bug reports due to silent memory corruption. Keith, is there a decent way to do that? For 2.4.17 it would help a lot... - 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/