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=-16.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham 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 864DBC433DB for ; Mon, 22 Mar 2021 13:00:52 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id E94D7619A6 for ; Mon, 22 Mar 2021 13:00:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E94D7619A6 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 9A4D06B00B3; Mon, 22 Mar 2021 08:42:00 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 92D9E6B00B5; Mon, 22 Mar 2021 08:42:00 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 7A8C76B00B9; Mon, 22 Mar 2021 08:42:00 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0053.hostedemail.com [216.40.44.53]) by kanga.kvack.org (Postfix) with ESMTP id 5B5546B00B3 for ; Mon, 22 Mar 2021 08:42:00 -0400 (EDT) Received: from smtpin33.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id BCB351804E52C for ; Mon, 22 Mar 2021 13:00:50 +0000 (UTC) X-FDA: 77947519860.33.1F654F8 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf16.hostedemail.com (Postfix) with ESMTP id 0ADAE8023256 for ; Mon, 22 Mar 2021 13:00:49 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id 3E51060C3D; Mon, 22 Mar 2021 13:00:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1616418044; bh=6SAcRO0qYg3edBZ6Nl5uqmHSmdsG/Cbc/xFrvoFFuDE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=J4EjrG0bjljNgV0UtyE8qwUzPFBRm26gliQFsU0gcVpujaNmPu60oYsKCOKJwCTQd 1RB3dQWr++7shv4lK5wknrzgFennM4ed58RJ5Pwcl1A42yqhBrEkTl9QpS61R5HnIX U0b6g8UFrC2qlwJsV0jRHZ94Qbno/jAf3N9dXqk22VlxqstMY1+L9WIa7oj5HFq2Zi LIrQNrLXn70I7qxurLHRrC6CV66KU82gM8F1rx8w4wx8eINXWWIyKz6vf+Te+f+z0E fBl4feSeG/FKt3kCmQOnte2V40OgcGswFD45NuY1PsCIb2cR6V3EL0fxF1xX/4CN2j 3ggkYu+Tmrdog== Date: Mon, 22 Mar 2021 15:00:37 +0200 From: Mike Rapoport To: Michal Hocko Cc: Bui Quang Minh , akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrea Arcangeli Subject: Re: [PATCH] userfaultfd: Write protect when virtual memory range has no page table entry Message-ID: References: <20210319152428.52683-1-minhquangbui99@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Stat-Signature: mkbka6tcbfd8hi7k1u3z5aygunmfnc74 X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 0ADAE8023256 Received-SPF: none (kernel.org>: No applicable sender policy available) receiver=imf16; identity=mailfrom; envelope-from=""; helo=mail.kernel.org; client-ip=198.145.29.99 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1616418049-863059 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, Mar 22, 2021 at 11:14:37AM +0100, Michal Hocko wrote: > Le'ts Andrea and Mike > > On Fri 19-03-21 22:24:28, Bui Quang Minh wrote: > > userfaultfd_writeprotect() use change_protection() to clear write bit in > > page table entries (pte/pmd). So, later write to this virtual address > > range causes a page fault, which is then handled by userspace program. > > However, change_protection() has no effect when there is no page table > > entries associated with that virtual memory range (a newly mapped memory > > range). As a result, later access to that memory range causes allocating a > > page table entry with write bit still set (due to VM_WRITE flag in > > vma->vm_flags). > > > > Add checks for VM_UFFD_WP in vma->vm_flags when allocating new page table > > entry in missing page table entry page fault path. > > From the above it is not really clear whether this is a usability > problem or a bug of the interface. I'd say it's usability/documentation clarity issue. Userspace can register an area with UFFDIO_REGISTER_MODE_MISSING | UFFDIO_REGISTER_MODE_WP and then it will be notified either when page table has no entry for a virtual address or when there is a write to a write protected address. > > Signed-off-by: Bui Quang Minh > > --- > > mm/huge_memory.c | 12 ++++++++++++ > > mm/memory.c | 10 ++++++++++ > > 2 files changed, 22 insertions(+) > > > > diff --git a/mm/huge_memory.c b/mm/huge_memory.c > > index ae907a9c2050..9bb16a55a48c 100644 > > --- a/mm/huge_memory.c > > +++ b/mm/huge_memory.c > > @@ -636,6 +636,11 @@ static vm_fault_t __do_huge_pmd_anonymous_page(struct vm_fault *vmf, > > > > entry = mk_huge_pmd(page, vma->vm_page_prot); > > entry = maybe_pmd_mkwrite(pmd_mkdirty(entry), vma); > > + if (userfaultfd_wp(vma)) { > > + entry = pmd_wrprotect(entry); > > + entry = pmd_mkuffd_wp(entry); > > + } > > + > > page_add_new_anon_rmap(page, vma, haddr, true); > > lru_cache_add_inactive_or_unevictable(page, vma); > > pgtable_trans_huge_deposit(vma->vm_mm, vmf->pmd, pgtable); > > @@ -643,6 +648,13 @@ static vm_fault_t __do_huge_pmd_anonymous_page(struct vm_fault *vmf, > > update_mmu_cache_pmd(vma, vmf->address, vmf->pmd); > > add_mm_counter(vma->vm_mm, MM_ANONPAGES, HPAGE_PMD_NR); > > mm_inc_nr_ptes(vma->vm_mm); > > + > > + if (userfaultfd_huge_pmd_wp(vma, *vmf->pmd)) { > > + spin_unlock(vmf->ptl); > > + count_vm_event(THP_FAULT_ALLOC); > > + count_memcg_event_mm(vma->vm_mm, THP_FAULT_ALLOC); > > + return handle_userfault(vmf, VM_UFFD_WP); > > + } > > spin_unlock(vmf->ptl); > > count_vm_event(THP_FAULT_ALLOC); > > count_memcg_event_mm(vma->vm_mm, THP_FAULT_ALLOC); > > diff --git a/mm/memory.c b/mm/memory.c > > index 5efa07fb6cdc..b835746545bf 100644 > > --- a/mm/memory.c > > +++ b/mm/memory.c > > @@ -3564,6 +3564,11 @@ static vm_fault_t do_anonymous_page(struct vm_fault *vmf) > > if (vma->vm_flags & VM_WRITE) > > entry = pte_mkwrite(pte_mkdirty(entry)); > > > > + if (userfaultfd_wp(vma)) { > > + entry = pte_wrprotect(entry); > > + entry = pte_mkuffd_wp(entry); > > + } > > + > > vmf->pte = pte_offset_map_lock(vma->vm_mm, vmf->pmd, vmf->address, > > &vmf->ptl); > > if (!pte_none(*vmf->pte)) { > > @@ -3590,6 +3595,11 @@ static vm_fault_t do_anonymous_page(struct vm_fault *vmf) > > > > /* No need to invalidate - it was non-present before */ > > update_mmu_cache(vma, vmf->address, vmf->pte); > > + > > + if (userfaultfd_pte_wp(vma, *vmf->pte)) { > > + pte_unmap_unlock(vmf->pte, vmf->ptl); > > + return handle_userfault(vmf, VM_UFFD_WP); > > + } > > unlock: > > pte_unmap_unlock(vmf->pte, vmf->ptl); > > return ret; > > -- > > 2.25.1 > > -- > Michal Hocko > SUSE Labs -- Sincerely yours, Mike.