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
| ||
|
Date: Sun, 27 Oct 2019 11:30:21 +0100 From: Florian Weimer <fw@...eb.enyo.de> To: Mike Rapoport <rppt@...nel.org> Cc: linux-kernel@...r.kernel.org, Alexey Dobriyan <adobriyan@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, Andy Lutomirski <luto@...nel.org>, Arnd Bergmann <arnd@...db.de>, Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>, James Bottomley <jejb@...ux.ibm.com>, Peter Zijlstra <peterz@...radead.org>, Steven Rostedt <rostedt@...dmis.org>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, linux-api@...r.kernel.org, linux-mm@...ck.org, x86@...nel.org, Mike Rapoport <rppt@...ux.ibm.com> Subject: Re: [PATCH RFC] mm: add MAP_EXCLUSIVE to create exclusive user mappings * Mike Rapoport: > The patch below aims to allow applications to create mappins that have > pages visible only to the owning process. Such mappings could be used to > store secrets so that these secrets are not visible neither to other > processes nor to the kernel. How is this expected to interact with CRIU? > I've only tested the basic functionality, the changes should be verified > against THP/migration/compaction. Yet, I'd appreciate early feedback. What are the expected semantics for VM migration? Should it fail?
Powered by blists - more mailing lists