| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20080908143003.GB10580@elte.hu> Date: Mon, 8 Sep 2008 16:30:03 +0200 From: Ingo Molnar <mingo@...e.hu> To: Bodo Eggert <7eggert@....de> Cc: Luca Tettamanti <kronos.it@...il.com>, "H. Peter Anvin" <hpa@...nel.org>, Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org, mingo@...hat.com Subject: Re: [2.6.27] overlapping early reservations [was: early exception - lockdep related?] * Bodo Eggert <7eggert@....de> wrote: > Ingo Molnar <mingo@...e.hu> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists