From: Ingo Molnar <mingo@elte.hu>
To: Bodo Eggert <7eggert@gmx.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
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
Date: Wed, 14 Jan 2009 06:45:56 +0100 [thread overview]
Message-ID: <20090114054556.GB11153@elte.hu> (raw)
In-Reply-To: <E1LMstm-0001QW-7i@be1.7eggert.dyndns.org>
* Bodo Eggert <7eggert@gmx.de> wrote:
> If the initrd is not decompressed successfully, [...]
No, that's not the issue - i think hpa's description was misleading in
that respect.
This is not some sort of corruption. I have hit this pointless panic
during testing: there was nothing wrong with either the initrd or the
system, the bzImage simply did not include the right decompressor .config
option to even read the initrd.
The analogue is if i booted a kernel with CONFIG_MODULES disabled. I do it
all the time, it always worked without problems and the initrd with
modules in it cannot be interpreted in any sane way CONFIG_MODULES - still
it works just fine because the initrd is uninteresting as far as the
modules go.
So basically now the kernel has regressed in its bzImage utility: "oh, i
dont have a decompressor for the initrd. PANIC!". And that is a step
backwards. Unless you use bzImage i dont think you can really appreciate
this argument.
I would not mind a warning message though, that bit makes sense.
Ingo
next prev parent reply other threads:[~2009-01-14 5:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bU0fj-7Ap-43@gated-at.bofh.it>
2009-01-13 23:42 ` Bodo Eggert
2009-01-14 5:45 ` Ingo Molnar [this message]
2009-01-14 6:47 ` Alain Knaff
2009-01-14 7:45 ` Ingo Molnar
2009-01-14 15:19 ` Bodo Eggert
[not found] ` <bU0If-8vA-19@gated-at.bofh.it>
[not found] ` <bU6NE-1bi-3@gated-at.bofh.it>
[not found] ` <bU837-3lq-11@gated-at.bofh.it>
[not found] ` <bU8FR-4by-23@gated-at.bofh.it>
[not found] ` <bU9iw-5gV-1@gated-at.bofh.it>
[not found] ` <bUbkj-8un-5@gated-at.bofh.it>
2009-01-14 18:35 ` Bodo Eggert
[not found] ` <bUi2r-2kd-13@gated-at.bofh.it>
2009-01-18 12:55 ` Bodo Eggert
2009-01-13 22:38 H. Peter Anvin
2009-01-13 23:17 ` Alain Knaff
2009-01-14 5:40 ` Ingo Molnar
2009-01-14 7:02 ` Alain Knaff
2009-01-14 7:48 ` Ingo Molnar
2009-01-14 8:23 ` Alain Knaff
2009-01-14 10:37 ` Ingo Molnar
2009-01-14 17:42 ` H. Peter Anvin
2009-01-14 1:18 ` Theodore Tso
2009-01-14 6:51 ` Alain Knaff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090114054556.GB11153@elte.hu \
--to=mingo@elte.hu \
--cc=7eggert@gmx.de \
--cc=alain@knaff.lu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®