linux-kernel - [RFC 3/3] x86, mirror: x86 enabling - find mirrored memory ranges and tell memblock

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: <7bdbb1a569d487b3a772fbb7b66b9498d6cee551.1423259664.git.tony.luck@intel.com>
Date:	Tue, 3 Feb 2015 14:40:19 -0800
From:	Tony Luck <tony.luck@...el.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...r.kernel.org
Subject: [RFC 3/3] x86, mirror: x86 enabling - find mirrored memory ranges
 and tell memblock

Can't post this part yet because it uses things in an upcoming[*] ACPI, UEFI, or some
other four-letter-ending-in-I standard.  So just imagine a call someplace early
in startup that reads information about mirrored address ranges and does:

+	for (...) {
+		start = ...;
+		size = ...;
+		if (it looks mirrored)
+			memblock_mark_mirror(start, size);
+	}

Whole patch is pretty tiny:

 3 files changed, 19 insertions(+)

How much damage could I possibly do in just 19 lines?

-Tony

[*] very soon, I'm told
--
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/