From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Weimer Subject: Re: [PATCH RFC] mm: add MAP_EXCLUSIVE to create exclusive user mappings Date: Sun, 27 Oct 2019 11:30:21 +0100 Message-ID: <87d0eieb0i.fsf@mid.deneb.enyo.de> References: <1572171452-7958-1-git-send-email-rppt@kernel.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <1572171452-7958-1-git-send-email-rppt@kernel.org> (Mike Rapoport's message of "Sun, 27 Oct 2019 12:17:31 +0200") Sender: linux-kernel-owner@vger.kernel.org To: Mike Rapoport Cc: linux-kernel@vger.kernel.org, Alexey Dobriyan , Andrew Morton , Andy Lutomirski , Arnd Bergmann , Borislav Petkov , Dave Hansen , James Bottomley , Peter Zijlstra , Steven Rostedt , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , linux-api@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org, Mike Rapoport List-Id: linux-api@vger.kernel.org * 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?