[PATCH 1/1] init:add boot option "initramfs_packnum"

From: Zhen Lei
Date: Mon Nov 10 2014 - 20:48:05 EST


During the development phase, we usually enlarge initrd-end to reserve more
memory than the initfs zip exactly occupied. Then we can easily add or delete
files in zip package, without generate fdt again and again. But unfortunately,
if too many zeros followed initfs zip, it will take a long time to break the
loop.

while (!message && len) {
... ...
if (!*buf) {
buf++;
... ...
continue;
}

So, use the boot option "initramfs_packnum" to specify how many zip packages
in each initrd area. When the specified number of packages decompressed in one
area, immediately terminate the loop. Have no impact on current use by default.

Signed-off-by: Zhen Lei <thunder.leizhen@xxxxxxxxxx>
---
init/initramfs.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)

diff --git a/init/initramfs.c b/init/initramfs.c
index ad1bd77..356764f 100644
--- a/init/initramfs.c
+++ b/init/initramfs.c
@@ -446,12 +446,24 @@ static unsigned long my_inptr; /* index of next byte to be processed in inbuf */

#include <linux/decompress/generic.h>

+/* zero and negative means packages number is unlimited */
+static int initramfs_packnum __initdata;
+
+static __init int setup_initramfs_packnum(char *str)
+{
+ get_option(&str, &initramfs_packnum);
+
+ return 0;
+}
+early_param("initramfs_packnum", setup_initramfs_packnum);
+
static char * __init unpack_to_rootfs(char *buf, unsigned long len)
{
long written;
decompress_fn decompress;
const char *compress_name;
static __initdata char msg_buf[64];
+ int packnum = initramfs_packnum;

header_buf = kmalloc(110, GFP_KERNEL);
symlink_buf = kmalloc(PATH_MAX + N_ALIGN(PATH_MAX) + 1, GFP_KERNEL);
@@ -500,6 +512,9 @@ static char * __init unpack_to_rootfs(char *buf, unsigned long len)
this_header = saved_offset + my_inptr;
buf += my_inptr;
len -= my_inptr;
+
+ if (!(--packnum))
+ break;
}
dir_utime();
kfree(name_buf);
--
1.8.0


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/