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: <20140622212959.GA766@arch.cereza>
Date:	Sun, 22 Jun 2014 18:30:00 -0300
From:	Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	Ezequiel Garcia <ezequiel@...guardiasur.com.ar>,
	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Guido Martínez <guido@...guardiasur.com.ar>
Subject: Re: [PATCH] init: Introduce 'noinitramfs' kernel parameter

Hi Henrique,

On 22 Jun 11:53 AM, Henrique de Moraes Holschuh wrote:
> On Sun, 22 Jun 2014, Ezequiel Garcia wrote:
> > This commit adds a new kernel parameter to provide such option, following the
> > naming of the current 'initrd' which serves a similar purpose, for an initial
> > RAM disk.
> 
> How does it interact with the early initramfs?
> 
> Maybe we should have the options to ignore both, ignore just the early
> initramfs (to skip microcode updates and ACPI table updates), and ignore
> just the main initramfs?
> 

I must admit I don't have much experience with any "earlier" initramfs.
Maybe you can point me at some links about this?

Unless I'm missing something, this "early" initramfs is an userspace artifact
in the construction of the initramfs, so the kernel has no way to distinguish
one from the other. Thus, we cannot mount one and not the other.
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ