linux-kernel - Re: The policy on initramfs decompression failure

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

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

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

Date:	Wed, 14 Jan 2009 08:45:42 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Alain Knaff <alain@...ff.lu>
Cc:	Bodo Eggert <7eggert@....de>, "H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Al Viro <viro@....linux.org.uk>
Subject: Re: The policy on initramfs decompression failure


* Alain Knaff <alain@...ff.lu> wrote:

> > Unless you use bzImage i dont think you can really appreciate this 
> > argument.
> 
> Maybe that's the source of our misunderstanding. What is this bzImage? 
> (I suppose it's not just the kernel name/format but something more. But 
> what?)

pure bzImages is what many kernel developers use to boot static kernel 
images, with drivers built in, often with no module support, etc.:

 $ make help | grep -i bzImage
 * bzImage      - Compressed kernel image (arch/x86/boot/bzImage)

the bzImage method never led to a panic related to a ramdisk before 
(unless the ramdisk was materially corrupted - which is not the case 
here), and should not lead to a panic afterwards either.

We use panics/crashes when the kernel meets a problem that makes 
continuing impossible, but that is not an issue here.

	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/