linux-kernel - Re: [PATCH part2 v2 0/8] Arrange hotpluggable memory as ZONE

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

Message-ID: <20131016070343.GD22509@gmail.com>
Date:	Wed, 16 Oct 2013 09:03:44 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Yinghai Lu <yinghai@...nel.org>, Tejun Heo <tj@...nel.org>,
	Zhang Yanfei <zhangyanfei.yes@...il.com>,
	Zhang Yanfei <zhangyanfei@...fujitsu.com>,
	Toshi Kani <toshi.kani@...com>, Ingo Molnar <mingo@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH part2 v2 0/8] Arrange hotpluggable memory as ZONE_MOVABLE

* H. Peter Anvin <hpa@...or.com> wrote:

> On 10/14/2013 11:50 PM, Ingo Molnar wrote:
> > 
> > So if anyone can implement it using huge pages, with a really fast 
> > __va() and __pa() implementation, then it might be possible. But 
> > that's a pretty major surgery on x86.
> 
> Well, we already *have* a way to deal with that for Xen (by inserting an 
> otherwise nonexistent logical level.)  I'm wondering if those interfaces 
> could be (ab)used for this as well, or if that is functionally 
> equivalent to saying that this should be done in a hypervisor.

It's not _that_ complex, and it does not need a separate security layer.

I have this distinct memory that I saw working patches that have paged all 
of the kernel's data, more than a decade ago. It was all rather 
disgusting, because those patches worked on the 4K level - but if a 2MB 
granular solution can be found in an elegant fashion then I think we could 
reconsider.

It definitely wasn't hypervisor thick. It probably needs a good hash for 
virtual address transformations, and all DMA has to be managed [these days 
we do that via the IOMMU anyway] but that's pretty much all - kernel 
virtual memory is reconfigured extremely rarely, so all that could be sped 
up for reads and mirrored per node and kept lockless, etc. etc. [Plus a 
metric ton of details.]

Thanks,

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