linux-kernel - Re: [2.6.27] overlapping early reservations [was: early exception

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 PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 07 Sep 2008 18:47:33 +0200
From:	Bodo Eggert <7eggert@....de>
To:	Ingo Molnar <mingo@...e.hu>, 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?]

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.

I had a similar bug in PAM: One of these modules has a parameter to invert
the check. I copied the tested configuration to an old debian system, which
did not have this parameter, and it decided to ignore it (as if I were just
joking while writing the config files of a security system). Therefore the
system was open for everybody who was not supposed to use it.

I don't think ignoring an intrd will be as serious, but having a panic (and
a timeout) is preferable to starting the wrong configuration.

--
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/