Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp653617pxb; Tue, 2 Feb 2021 14:28:33 -0800 (PST) X-Google-Smtp-Source: ABdhPJyNOKQrqMCY63DPWAzHc14+fTOn17RVmkdgZMJJDQFmLzqFqL7p7sFjiLJrf4PGdNdr+cHc X-Received: by 2002:a17:906:607:: with SMTP id s7mr155907ejb.301.1612304912814; Tue, 02 Feb 2021 14:28:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612304912; cv=none; d=google.com; s=arc-20160816; b=PCM52s9f90/sai+QeBbKQ50FxhcgRWIlEIHnm2UwrQOqMxG+5ryEKFn/xhe8KcNwQt VGJTOm5HGpQLL7C2vL0QGvbrJv8TwbJCimXhxar7Mb/GrcHJacffS1Q4FxitdDm0yqvY ESvqipQuFtGRKKB7qJLfxAy5CWuEI81pFyjuSyj6PJkrBjvtHWuaieBLfGMngy6G4zMs HHEZGdKac6i5cXF0DiYRkZqEmJ45+NjqgWxrJ4No4McTKysEiqLQizAebvknmfphCPXf MjzN0HsDw5w0kkOVtQJcGy2CSL5XBdlGobdA6DXta6uTXUpkGX7+zetJvcoqKKWcw4ty ANiQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:organization :from:references:cc:to:subject:dkim-signature; bh=DMQGIZBX3ZSdULucq6YnujqHSWIcTSgvTL7Om1Dz16I=; b=DkaHQ8bQoQJZWymilQ8qipN2//+L+jmVtDnNby+JiWJ1B7J73IquWcBDH3wjlWymYZ AYlSQj7kQNJINS6hSlu5ajIzxFTpWTcZU14Gx9fnk0zyFcss5J13/7s7o/Fumjyb5056 dzy4ceAqh458tPhq3K+qd45XRfn8JGGdBWCM8Ty277+zxCHkwsqyvnLkYTQ5eT+rcKYy uAX8yd6A4GYqlddEV0afamLAhVyuCBEXGdK3XQcieJX3Gwpmrd+YUjLh6DPACVnDh56d rGQdRzeCmG8MtIzHGrARGN5DZQelNvo1vpI5iY6ZNcbuypCvxWQQLZH4Sdzbl5jvU9bU Jbng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=TB4f54GA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id se3si128828ejb.303.2021.02.02.14.28.06; Tue, 02 Feb 2021 14:28:32 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=TB4f54GA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234020AbhBBOrb (ORCPT + 99 others); Tue, 2 Feb 2021 09:47:31 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:47656 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234614AbhBBOgT (ORCPT ); Tue, 2 Feb 2021 09:36:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1612276493; 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=DMQGIZBX3ZSdULucq6YnujqHSWIcTSgvTL7Om1Dz16I=; b=TB4f54GA6of7/fhHlL/DuK168L4SCX0eFlv9Nj8+BS15mujoNNh6Zh3wB3ferDM6D4LsUp RzxQbicNJa2cuAV1vIX2jC3Yl57abYxTir8Gadw03l/KFjyRH7KGgjWtMYBNIb+ZwZ/p1A F/GWWPlOnXmMZeSqeqhRJ/9dts0hSrg= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-464-dkvrsbKJMeCl98dqyoVbLw-1; Tue, 02 Feb 2021 09:34:48 -0500 X-MC-Unique: dkvrsbKJMeCl98dqyoVbLw-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0E886184DBF0; Tue, 2 Feb 2021 14:34:44 +0000 (UTC) Received: from [10.36.114.148] (ovpn-114-148.ams2.redhat.com [10.36.114.148]) by smtp.corp.redhat.com (Postfix) with ESMTP id 505D15D9C6; Tue, 2 Feb 2021 14:34:36 +0000 (UTC) Subject: Re: [PATCH v16 07/11] secretmem: use PMD-size pages to amortize direct map fragmentation To: Michal Hocko Cc: Mike Rapoport , James Bottomley , Andrew Morton , Alexander Viro , Andy Lutomirski , Arnd Bergmann , Borislav Petkov , Catalin Marinas , Christopher Lameter , Dan Williams , Dave Hansen , Elena Reshetova , "H. Peter Anvin" , Ingo Molnar , "Kirill A. Shutemov" , Matthew Wilcox , Mark Rutland , Mike Rapoport , Michael Kerrisk , Palmer Dabbelt , Paul Walmsley , Peter Zijlstra , Rick Edgecombe , Roman Gushchin , Shakeel Butt , Shuah Khan , Thomas Gleixner , Tycho Andersen , Will Deacon , linux-api@vger.kernel.org, linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-nvdimm@lists.01.org, linux-riscv@lists.infradead.org, x86@kernel.org, Hagen Paul Pfeifer , Palmer Dabbelt References: <73738cda43236b5ac2714e228af362b67a712f5d.camel@linux.ibm.com> <6de6b9f9c2d28eecc494e7db6ffbedc262317e11.camel@linux.ibm.com> <20210202124857.GN242749@kernel.org> <6653288a-dd02-f9de-ef6a-e8d567d71d53@redhat.com> <211f0214-1868-a5be-9428-7acfc3b73993@redhat.com> From: David Hildenbrand Organization: Red Hat GmbH Message-ID: <95625b83-f7e2-b27a-2b99-d231338047fb@redhat.com> Date: Tue, 2 Feb 2021 15:34:29 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.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 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02.02.21 15:32, Michal Hocko wrote: > On Tue 02-02-21 15:26:20, David Hildenbrand wrote: >> On 02.02.21 15:22, Michal Hocko wrote: >>> On Tue 02-02-21 15:12:21, David Hildenbrand wrote: >>> [...] >>>> I think secretmem behaves much more like longterm GUP right now >>>> ("unmigratable", "lifetime controlled by user space", "cannot go on >>>> CMA/ZONE_MOVABLE"). I'd either want to reasonably well control/limit it or >>>> make it behave more like mlocked pages. >>> >>> I thought I have already asked but I must have forgotten. Is there any >>> actual reason why the memory is not movable? Timing attacks? >> >> I think the reason is simple: no direct map, no copying of memory. > > This is an implementation detail though and not something terribly hard > to add on top later on. I was more worried there would be really > fundamental reason why this is not possible. E.g. security implications. I don't remember all the details. Let's see what Mike thinks regarding migration (e.g., security concerns). -- Thanks, David / dhildenb