Message-ID: <496D8B55.2000901@knaff.lu>
Date: Wed, 14 Jan 2009 07:51:01 +0100
From: Alain Knaff <alain@knaff.lu>
User-Agent: Thunderbird 2.0.0.18 (X11/20081125)
MIME-Version: 1.0
To: Theodore Tso <tytso@mit.edu>, "H. Peter Anvin" <hpa@zytor.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
       Al Viro <viro@ftp.linux.org.uk>, Alain Knaff <alain@knaff.lu>
Subject: Re: The policy on initramfs decompression failure
References: <496D17F9.8080605@zytor.com> <20090114011844.GD14730@mit.edu>
In-Reply-To: <20090114011844.GD14730@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1247
Lines: 33

Theodore Tso wrote:
>    failed-initramfs-decode=panic      Panic on failed initramfs
>    failed-initramfs-decode=partial    If the initramfs fails part-way in, 
>    				      decode what you can and let the boot
> 				      system see what files could be fully
> 				      decypted
>    failed-initramfs-decode=allow      If the initramfs decryption fails
>    				      part-of-the-way in, continue the
> 				      boot, but do not provide the partial
> 				      initramfs --- i.e., this is the 
> 				      all-or-nothing option

Interesting approach... but wouldn't it make more sense to have that be
global? Or else, eventually every single panic will have such a
tri-state switch, with associated option parsing and overhead, leading
to bloat.

> If this is too complicated, I'd be happy with the "panic on failed
> initramfs".  After all, the user can always simply delete the initrd
> specifier from their grub boot configuration, and simply retry the
> boot....

Exactly!

Regards,

Alain

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