linux-kernel - Early cpio decoder and ACPI table override via initrd making use of it

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-next>] [day] [month] [year] [list]

Date:	Thu, 30 Aug 2012 11:29:15 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	hpa@...or.com
Cc:	linux-kernel@...r.kernel.org, lenb@...nel.org,
	robert.moore@...el.com, ming.m.lin@...el.com,
	initramfs@...r.kernel.org, bigeasy@...utronix.de, vojcek@...n.pl,
	eric.piel@...mplin-utc.net, linux-acpi@...r.kernel.org,
	yinghai@...nel.org
Subject: Early cpio decoder and ACPI table override via initrd making use of it

This is based on the early cpio decoder from hpa.
The first patch is exactly the patch (41750d31fc9599fd81763e685) from git repo:
kernel/git/hpa/linux-earlyinitramfs. Ony the Makefile was slightly
adjusted to latest Linus kernel (3.6.0-rc3).

Because of the special requirements hpa mentioned, I gave up the cleaner
callback approach. It may make sense to revive it if there are potential
more users and let the very early code call the cpio decoder directly and
let others use the callback interface I had made up.

Anyway, it would be great to see these two patches showing up in a
mainline branch and linux-next asap, so that they can slip in with the next
(3.7) merge window.

Working on ACPI features or debugging ACPI problems is a nightmare on Linux
currently. ACPI table overrding via initrd makes working on such problems
a lot easier.

   Thomas

--
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/