From: klightspeed@killerwolves.net (Ben Peddell)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC: tolerate junk after valid initramfs
Date: Thu, 25 Oct 2012 18:06:56 +1000 [thread overview]
Message-ID: <5088F320.6000806@killerwolves.net> (raw)
At the moment, the initramfs handling code will reject a valid initramfs
if there is junk between the end of the valid initramfs and the
initramfs size given to the kernel.
For example passing initrd=0x01000000,4M will not work unless the
initramfs is either exactly 4M in size or is padded with zeroes up to 4M.
As those working with ARM processors might know, the initialization code
in the bootloader generally doesn't zero out unused memory, so that
memory will contain garbage.
What downsides are there to patching init/initramfs.c to have the kernel
accept valid initramfs images where the image is shorter than the length
passed to the kernel by the bootloader?
reply other threads:[~2012-10-25 8:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5088F320.6000806@killerwolves.net \
--to=klightspeed@killerwolves.net \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).