Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp576035ybx; Wed, 30 Oct 2019 01:19:15 -0700 (PDT) X-Google-Smtp-Source: APXvYqz2ILXG9MtKu5Ym2f2E0u2qvVHXPTl8E+L5XtPHh6xW4ZlI5923GhiEBSZJEyEtkAClwYE2 X-Received: by 2002:a05:6402:1816:: with SMTP id g22mr30390559edy.76.1572423555152; Wed, 30 Oct 2019 01:19:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572423555; cv=none; d=google.com; s=arc-20160816; b=daUiqOPsYOOppL0Bg/fGAeHpZ1acQEMAtgoyfz1BF02h6u/4fcgmsm+HOzsL72bLLc RZiX4wn7v4jzM5AnzdSmZREXT1D76/PE6pZItSQo7ZgizPbWNdyiOvzCBT+wCYqzZe+W G/4c6R7rCdjbmpUwtfdAA48f071CgUCfirhMQP82BMt4JlEYA6L96hjvoNnmOLSmmEIF qX+AwcEnYG8LwUk08kWFk/PKzHYvNQfUCFM6re6McD9c065pGv78ZQMWvUPyrDvjnbrr Lg9995IneBpmIvuphiHzIrlBzUbTs6O4k/KXNpTFoEXizCJYZubwnRQGWpqEcB6jKfpu zzVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=eYADznOunvGbYqeSLQ4Qw20wWRaMJt/J8vHAI81uE/4=; b=vhnyL74KaoYRQkUTTemJk6evitXFtIjEgjtN26QSal/QUFYgcvvRXzoGwNJp4P6I+g OgHpyWoDFqY7ogpIhhsIhfGUuV6vaRxJgGZahKk7XD4krM0hwcRkMly81IyD3VzEznKA IVSEdZA9JQLSWPokFZcS+tRDFmkoKm5kxtZcAXlhMQzSM+ShtucS3OO0MBH6wqDGr1WU UIVCsTXmKp1RFgHkkCsImUMhR9ai/NuPPjx55mRhwjT296BopnL+NFwFKLeCinmrYRXC t+OWBlpGBS4q23KMn4b8S4dtxpASrQ3MrgxXT4wNNnrsFBRIW0kMbgOhqpwXT4gbYdJz MQLQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=FyAYL+pk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y38si918244edb.87.2019.10.30.01.18.51; Wed, 30 Oct 2019 01:19:15 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=FyAYL+pk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726239AbfJ3IPj (ORCPT + 99 others); Wed, 30 Oct 2019 04:15:39 -0400 Received: from mail.kernel.org ([198.145.29.99]:52790 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725822AbfJ3IPj (ORCPT ); Wed, 30 Oct 2019 04:15:39 -0400 Received: from rapoport-lnx (190.228.71.37.rev.sfr.net [37.71.228.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A9CC62067D; Wed, 30 Oct 2019 08:15:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1572423338; bh=iS1J5NyS2mmPn50lpxeYWffskvCfVMjwF0kqUnoxyWw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=FyAYL+pk/pQmtYM6DFquQE87kHJQ+2nodze4tZvavQE73bdBil7hC7rx+P9j1WuGU JlmZrz8Hf1kfu0trTmrlgRjxU+WoR1EdQemFlorT+lCJKW8ebDw74pSN9GIR0asSfK aPtAhhSUkxoe/pVNW25rZQ0PopjelW+Hk9lv1tBE= Date: Wed, 30 Oct 2019 09:15:30 +0100 From: Mike Rapoport To: David Hildenbrand 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 Subject: Re: [PATCH RFC] mm: add MAP_EXCLUSIVE to create exclusive user mappings Message-ID: <20191030081529.GB20624@rapoport-lnx> References: <1572171452-7958-1-git-send-email-rppt@kernel.org> <1572171452-7958-2-git-send-email-rppt@kernel.org> <085ed07e-e646-f7a4-0370-06f33a2a4e4a@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <085ed07e-e646-f7a4-0370-06f33a2a4e4a@redhat.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 29, 2019 at 12:02:34PM +0100, David Hildenbrand wrote: > On 27.10.19 11:17, Mike Rapoport wrote: > >From: Mike Rapoport > > > >The mappings created with MAP_EXCLUSIVE are visible only in the context of > >the owning process and can be used by applications to store secret > >information that will not be visible not only to other processes but to the > >kernel as well. > > > >The pages in these mappings are removed from the kernel direct map and > >marked with PG_user_exclusive flag. When the exclusive area is unmapped, > >the pages are mapped back into the direct map. > > > > Just a thought, the kernel is still able to indirectly read the contents of > these pages by doing a kdump from kexec environment, right? Right. > Also, I wonder > what would happen if you map such pages via /dev/mem into another user space > application and e.g., use them along with kvm [1]. Do you mean that one application creates MAP_EXCLUSIVE and another applications accesses the same physical pages via /dev/mem? With /dev/mem all physical memory is visible... > [1] https://lwn.net/Articles/778240/ > > -- > > Thanks, > > David / dhildenb > -- Sincerely yours, Mike.