From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753987AbYIHOaa (ORCPT ); Mon, 8 Sep 2008 10:30:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751963AbYIHOaW (ORCPT ); Mon, 8 Sep 2008 10:30:22 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:32855 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750885AbYIHOaW (ORCPT ); Mon, 8 Sep 2008 10:30:22 -0400 Date: Mon, 8 Sep 2008 16:30:03 +0200 From: Ingo Molnar To: Bodo Eggert <7eggert@gmx.de> Cc: Luca Tettamanti , "H. Peter Anvin" , Peter Zijlstra , linux-kernel@vger.kernel.org, mingo@redhat.com Subject: Re: [2.6.27] overlapping early reservations [was: early exception - lockdep related?] Message-ID: <20080908143003.GB10580@elte.hu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Bodo Eggert <7eggert@gmx.de> wrote: > Ingo Molnar wrote: > > > In any case it would make sense to turn that particular overlap > > situation into a warning message and disable initrd decompress - and > > try to boot with whatever is built-in the kernel. > > If I explicitely tell my system to load a ramdisk, ignoring it is a > bug. we dont really ignore it - we detect that it got corrupted by the bootloader. (it got overwritten by the kernel image - information has been destroyed irrevocably) how we react to that breakage we detect is up to debate: it's fine to try to continue (presumably a huge vmlinux means it has all the drivers already) - and if a system relies on an initrd it wont get fast in bootup anyway. that's why i suggested to print a warning, do a 5 seconds delay after that warning via mdelay(5000) so that the user has a chance to notice what is wrong, and then try to continue. Panicking is just as fine. Ingo