* [PATCH] initramfs: handle trailing junk after valid image
@ 2012-07-06 10:12 Ben Peddell
0 siblings, 0 replies; only message in thread
From: Ben Peddell @ 2012-07-06 10:12 UTC (permalink / raw)
To: linux-kernel
The initramfs handling since commit df37bd15 has been rejecting
valid images that have garbage after them. For example, on an
architecture where the initramfs address and size are specified
as a kernel parameter (specifically unicore32 and arm), specifying
e.g. initrd=0x01000000,4M will not work unless the image is padded
with nulls to 4MiB. This is unlikely to occur if the user is using
this parameter to work around a bug in the bootloader.
---
init/initramfs.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/init/initramfs.c b/init/initramfs.c
index 84c6bf1..26c2cb1 100644
--- a/init/initramfs.c
+++ b/init/initramfs.c
@@ -467,6 +467,9 @@ static char * __init unpack_to_rootfs(char *buf, unsigned len)
compress_name);
message = msg_buf;
}
+ } else if (state == Reset) {
+ my_inptr = len;
+ pr_warn("%s: junk at end of compressed archive\n", __func__);
} else
error("junk in compressed archive");
if (state != Reset)
--
1.7.3.4
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-07-06 10:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-06 10:12 [PATCH] initramfs: handle trailing junk after valid image Ben Peddell
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®