From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.3 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 76CE8C433FE for ; Wed, 15 Sep 2021 15:35:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 552BD610E9 for ; Wed, 15 Sep 2021 15:35:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234280AbhIOPhH (ORCPT ); Wed, 15 Sep 2021 11:37:07 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:49265 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234095AbhIOPhF (ORCPT ); Wed, 15 Sep 2021 11:37:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1631720145; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hLB4RIdMUuayuQDxk1drvnDwcRCYgf6RZ3NglDIohcw=; b=T0D9J7QxrQt7dA278sa3XHmvg9thuMJTlSPWlHQqIeuGX68+nwyv6V0IbgMCwQ91BF/Z88 GE4NDs7jKq87VaTRjZmQCNLraGnYNnjb12tCrcgaTln6+jiijpTDZ0pv78a/Eh+4Ihv2Mr imn+3BQQogpXBi18GetOqLPYZh7sFQM= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-217-jK6_uxvsM8SOdQ-iaelU0w-1; Wed, 15 Sep 2021 11:35:44 -0400 X-MC-Unique: jK6_uxvsM8SOdQ-iaelU0w-1 Received: by mail-wm1-f69.google.com with SMTP id b139-20020a1c8091000000b002fb33c467c8so1637224wmd.5 for ; Wed, 15 Sep 2021 08:35:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:from:to:cc:references:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=hLB4RIdMUuayuQDxk1drvnDwcRCYgf6RZ3NglDIohcw=; b=Tk48UjyFQEPmQhvllIiW1K1e6PRW5IOQQ6maIt/ld/yAn2+BcSDwClbN8UVMRxy1X5 wV2i0fzpqYPw7zrg24i7lKsSOuE5YQKuzulpeo3FyZ2MglF0fi8goo+YCJFXKStXAH2x qma9TsrK0WznHf3IcmBt3jz7sISkHRU80Zt7MVozjaHWnxMdv0F+/CJAfZUjI7HFKkat 2kQgP+xhKnuAZbd9vRj6WgvK5x1wV6JOVQBo7Msclnj3YF9Tn6Ws8TQJ2Q1kZ9XXABP+ zZzTzcta6mZ830bA0AbKyLyv0/dg/6mymTp5/lyImX51f7Ikk5bfIOrKK5QKXHf9FX3S Pf/A== X-Gm-Message-State: AOAM53314wzceNYjbR8dY3iQ13ykawGpLjJWlBkNCEa6EfRROp5QCiGc VzUpEnECuCPJZZdw7GBw2UcZXYE6msvMrwPsDaUOExfuqtaaz/N+2CCy/L47x4+V8dlZZlK3+Nw OD2vYQ06la1n6b4UaGfAbOv79 X-Received: by 2002:a5d:66d1:: with SMTP id k17mr681538wrw.200.1631720142823; Wed, 15 Sep 2021 08:35:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw5OWqaCDbnfPfYJivbWZX/tz0dw8poxVVs/OqIyOZE0YLU2lOPz/RKZDjKDqWUdl51wuaSBw== X-Received: by 2002:a5d:66d1:: with SMTP id k17mr681496wrw.200.1631720142598; Wed, 15 Sep 2021 08:35:42 -0700 (PDT) Received: from [192.168.3.132] (p5b0c6426.dip0.t-ipconnect.de. [91.12.100.38]) by smtp.gmail.com with ESMTPSA id h8sm4462077wmb.35.2021.09.15.08.35.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Sep 2021 08:35:41 -0700 (PDT) Subject: Re: [RFC] KVM: mm: fd-based approach for supporting KVM guest private memory From: David Hildenbrand To: "Kirill A. Shutemov" Cc: Chao Peng , "Kirill A. Shutemov" , Andy Lutomirski , Sean Christopherson , Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Borislav Petkov , Andrew Morton , Joerg Roedel , Andi Kleen , David Rientjes , Vlastimil Babka , Tom Lendacky , Thomas Gleixner , Peter Zijlstra , Ingo Molnar , Varad Gautam , Dario Faggioli , x86@kernel.org, linux-mm@kvack.org, linux-coco@lists.linux.dev, Kuppuswamy Sathyanarayanan , Dave Hansen , Yu Zhang References: <20210824005248.200037-1-seanjc@google.com> <20210902184711.7v65p5lwhpr2pvk7@box.shutemov.name> <20210903191414.g7tfzsbzc7tpkx37@box.shutemov.name> <02806f62-8820-d5f9-779c-15c0e9cd0e85@kernel.org> <20210910171811.xl3lms6xoj3kx223@box.shutemov.name> <20210915195857.GA52522@chaop.bj.intel.com> <51a6f74f-6c05-74b9-3fd7-b7cd900fb8cc@redhat.com> <20210915142921.bxxsap6xktkt4bek@black.fi.intel.com> Organization: Red Hat Message-ID: <09caba0b-6b3d-668f-312c-ed870379b669@redhat.com> Date: Wed, 15 Sep 2021 17:35:40 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> >>> who will actually do some kind of gfn-epfn etc. mapping, how we'll >>> forbid access to this memory e.g., via /proc/kcore or when dumping memory >> >> It's not aimed to prevent root to shoot into his leg. Root do root. > > IMHO being root is not an excuse to read some random file (actually used > in production environments) to result in the machine crashing. Not > acceptable for distributions. I just realized that reading encrypted memory should be ok and only writing is an issue, right? -- Thanks, David / dhildenb