linux-kernel - Re: RFC: initramfs unpack point and rules

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070412110637.GG4095@ftp.linux.org.uk>
Date:	Thu, 12 Apr 2007 12:06:37 +0100
From:	Al Viro <viro@....linux.org.uk>
To:	Krzysztof Halasa <khc@...waw.pl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: RFC: initramfs unpack point and rules

On Thu, Apr 05, 2007 at 02:34:39PM +0200, Krzysztof Halasa wrote:
> First problem: initramfs is unpacked way before console drivers
> are initialized, so you aren't going to see the panic():
> 
> init/initramfs.c:static int __init populate_rootfs(void)
> ...
> 		printk(KERN_INFO "Unpacking initramfs...");
> 		err = unpack_to_rootfs((char *)initrd_start,
> 			initrd_end - initrd_start, 0);
> 		if (err)
> 			panic(err);
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 		printk(" done\n");
> 		free_initrd();
> 
> I wonder why is initramfs unpacked that early, before most drivers?
> I'd expect it much later in the boot sequence, just before userspace
> and initial devices (/dev/console etc) are needed. Should it be moved
> there? populate_rootfs() unpacks both builtin and external initramfs.

Nope.  The point is to have it as early as possible, so that we had more
or less normal environment when drivers, etc. are being initialized.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/