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=-3.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no 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 CEB05C63798 for ; Tue, 24 Nov 2020 16:49:50 +0000 (UTC) Received: from ml01.01.org (ml01.01.org [198.145.21.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4B3C3206D9 for ; Tue, 24 Nov 2020 16:49:50 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="ZCuQvSCf" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4B3C3206D9 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvdimm-bounces@lists.01.org Received: from ml01.vlan13.01.org (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id C7380100EB831; Tue, 24 Nov 2020 08:49:49 -0800 (PST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=198.145.29.99; helo=mail.kernel.org; envelope-from=rppt@kernel.org; receiver= Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 1A429100EBBDE for ; Tue, 24 Nov 2020 08:49:47 -0800 (PST) Received: from kernel.org (unknown [77.125.7.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B0D65206D8; Tue, 24 Nov 2020 16:49:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1606236586; bh=ofUYlPrJWYYZntZI6e1UjFnjHWpt+ejZuqW8X4FikI4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ZCuQvSCf55hd5LYTHCkX7HoUl/qLUj9Aw9Qt2bN77Vq37ymtgqf1vlqa/54yGLfET 9NqEFDk66Auv1EyiIzF9GLhnJC21iAtMI/wvzWombNFNDkOObvxkdIL/h8j9OReeJM eznOp2166MiDXEFDWf7MpCnskhIQaw8NFBBtv2Qk= Date: Tue, 24 Nov 2020 18:49:30 +0200 From: Mike Rapoport To: Catalin Marinas Subject: Re: [PATCH v11 4/9] mm: introduce memfd_secret system call to create "secret" memory areas Message-ID: <20201124164930.GK8537@kernel.org> References: <20201124092556.12009-1-rppt@kernel.org> <20201124092556.12009-5-rppt@kernel.org> <20201124105947.GA5527@gaia> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20201124105947.GA5527@gaia> Message-ID-Hash: ASB6KRJ5263SKWTCT72RTMV66YLILDUI X-Message-ID-Hash: ASB6KRJ5263SKWTCT72RTMV66YLILDUI X-MailFrom: rppt@kernel.org X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation CC: Andrew Morton , Alexander Viro , Andy Lutomirski , Arnd Bergmann , Borislav Petkov , Christopher Lameter , Dave Hansen , David Hildenbrand , Elena Reshetova , "H. Peter Anvin" , Ingo Molnar , James Bottomley , "Kirill A. Shutemov" , Matthew Wilcox , Mark Rutland , Mike Rapoport , Michael Kerrisk , Palmer Dabbelt , Paul Walmsley , Peter Zijlstra , Rick Edgecombe , Roman Gushchin , 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 X-Mailman-Version: 3.1.1 Precedence: list List-Id: "Linux-nvdimm developer list." Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Tue, Nov 24, 2020 at 10:59:48AM +0000, Catalin Marinas wrote: > Hi Mike, > > On Tue, Nov 24, 2020 at 11:25:51AM +0200, Mike Rapoport wrote: > > +static vm_fault_t secretmem_fault(struct vm_fault *vmf) > > +{ > > + struct address_space *mapping = vmf->vma->vm_file->f_mapping; ... > > + > > + err = set_direct_map_invalid_noflush(page, 1); > > + if (err) > > + goto err_del_page_cache; > > On arm64, set_direct_map_default_noflush() returns 0 if !rodata_full but > no pgtable changes happen since the linear map can be a mix of small and > huge pages. The arm64 implementation doesn't break large mappings. I > presume we don't want to tell the user that the designated memory is > "secret" but the kernel silently ignored it. > > We could change the arm64 set_direct_map* to return an error, however, I > think it would be pretty unexpected for the user to get a fault when > trying to access it. It may be better to return a -ENOSYS or something > on the actual syscall if the fault-in wouldn't be allowed later. > > Alternatively, we could make the linear map always use pages on arm64, > irrespective of other config or cmdline options (maybe not justified > unless we have clear memsecret users). Yet another idea is to get > set_direct_map* to break pmd/pud mappings into pte but that's not always > possible without a stop_machine() and potentially disabling the MMU. My preference would be to check at secretmem initialization if set_direct_map_*() actually do anything and then return an error from the syscall if they are essentially nop. I'll update the patches with something like this in v12. > -- > Catalin -- Sincerely yours, Mike. _______________________________________________ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-leave@lists.01.org