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:	Fri, 21 Sep 2012 15:28:03 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	hpa@...or.com
Cc:	trenn@...e.de, initramfs@...r.kernel.org, robert.moore@...el.com,
	lenb@...nel.org, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, yinghai@...nel.org,
	eric.piel@...mplin-utc.net
Subject: Early cpio decoder and ACPI table override via initrd making use of it

Should still apply on latest Linux tree, I can resubmit if not.
Would be great if hpa can push this into a x86 branch to get
this into linux-next and into Linus' tree with the next merge
window.

Thanks,

    Thomas

Dmesg output of a quick test:
 FACP ACPI table found in initrd [kernel/firmware/acpi/facp.aml][0xf4]
 DSDT ACPI table found in initrd [kernel/firmware/acpi/dsdt.aml][0x333c]
 e820: modified physical RAM map:
...
   modified: [mem 0x00000000f7fec000-0x00000000f7fef42f] ACPI data
...
 Disabling lock debugging due to kernel taint
 ACPI: Override [FACP-OEMFACP ], this is unsafe: tainting kernel
 ACPI: FACP 00000000f7ff0281 Physical table override, new table: ffffffffff4b7000
 ACPI: FACP 00000000f7fec000 000F4 (v03 A M I  OEMFACP  08000713 INTL 20120518)
 ACPI: Override [DSDT-0AAAA001], this is unsafe: tainting kernel
 ACPI: DSDT 00000000f7ff0410 Physical table override, new table: ffffffffff4b70f4
 ACPI: DSDT 00000000f7fec0f4 0333C (v01  0AAAA 0AAAA001 00000001 INTL 20120518)

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