From: Brian Geffon <bgeffon@google.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Zi Yan <ziy@nvidia.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Suren Baghdasaryan <surenb@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@redhat.com>,
stable@vger.kernel.org, Hugh Dickins <hughd@google.com>,
Marek Maslanka <mmaslanka@google.com>
Subject: Re: [PATCH v2] mm: fix finish_fault() handling for large folios
Date: Thu, 27 Feb 2025 11:47:02 -0500 [thread overview]
Message-ID: <CADyq12zgFigdBHiCv=AkZNLfbrmnCe2AVVOkjxNy9PwvJZsETQ@mail.gmail.com> (raw)
In-Reply-To: <19624e55-ba41-41e7-ba11-38b6ab3b96e5@linux.alibaba.com>
On Thu, Feb 27, 2025 at 2:34 AM Baolin Wang
<baolin.wang@linux.alibaba.com> wrote:
>
>
>
> On 2025/2/27 00:23, Brian Geffon wrote:
> > When handling faults for anon shmem finish_fault() will attempt to install
> > ptes for the entire folio. Unfortunately if it encounters a single
> > non-pte_none entry in that range it will bail, even if the pte that
> > triggered the fault is still pte_none. When this situation happens the
> > fault will be retried endlessly never making forward progress.
> >
> > This patch fixes this behavior and if it detects that a pte in the range
> > is not pte_none it will fall back to setting a single pte.
> >
> > Cc: stable@vger.kernel.org
> > Cc: Hugh Dickins <hughd@google.com>
> > Fixes: 43e027e41423 ("mm: memory: extend finish_fault() to support large folio")
> > Suggested-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> > Reported-by: Marek Maslanka <mmaslanka@google.com>
> > Signed-off-by: Brian Geffon <bgeffon@google.com>
> > ---
> > mm/memory.c | 15 ++++++++++-----
> > 1 file changed, 10 insertions(+), 5 deletions(-)
> >
> > diff --git a/mm/memory.c b/mm/memory.c
> > index b4d3d4893267..b6c467fdbfa4 100644
> > --- a/mm/memory.c
> > +++ b/mm/memory.c
> > @@ -5183,7 +5183,11 @@ vm_fault_t finish_fault(struct vm_fault *vmf)
> > bool is_cow = (vmf->flags & FAULT_FLAG_WRITE) &&
> > !(vma->vm_flags & VM_SHARED);
> > int type, nr_pages;
> > - unsigned long addr = vmf->address;
> > + unsigned long addr;
> > + bool needs_fallback = false;
> > +
> > +fallback:
> > + addr = vmf->address;
> >
> > /* Did we COW the page? */
> > if (is_cow)
> > @@ -5222,7 +5226,8 @@ vm_fault_t finish_fault(struct vm_fault *vmf)
> > * approach also applies to non-anonymous-shmem faults to avoid
> > * inflating the RSS of the process.
> > */
> > - if (!vma_is_anon_shmem(vma) || unlikely(userfaultfd_armed(vma))) {
> > + if (!vma_is_anon_shmem(vma) || unlikely(userfaultfd_armed(vma)) ||
> > + unlikely(needs_fallback)) {
>
> Nit: can you align the code? Otherwise look good to me.
I mailed a v3 with adjusted alignment, I'll let Andrew decide which
variation he prefers.
>
> > nr_pages = 1;
> > } else if (nr_pages > 1) {
> > pgoff_t idx = folio_page_idx(folio, page);
> > @@ -5258,9 +5263,9 @@ vm_fault_t finish_fault(struct vm_fault *vmf)
> > ret = VM_FAULT_NOPAGE;
> > goto unlock;
> > } else if (nr_pages > 1 && !pte_range_none(vmf->pte, nr_pages)) {
> > - update_mmu_tlb_range(vma, addr, vmf->pte, nr_pages);
> > - ret = VM_FAULT_NOPAGE;
> > - goto unlock;
> > + needs_fallback = true;
> > + pte_unmap_unlock(vmf->pte, vmf->ptl);
> > + goto fallback;
> > }
> >
> > folio_ref_add(folio, nr_pages - 1);
Thanks for looking
Brian
next prev parent reply other threads:[~2025-02-27 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 11:48 [PATCH] " Brian Geffon
2025-02-26 14:03 ` Matthew Wilcox
2025-02-26 14:31 ` Brian Geffon
2025-02-26 15:42 ` David Hildenbrand
2025-02-26 16:28 ` Matthew Wilcox
2025-02-26 16:52 ` David Hildenbrand
2025-02-26 15:17 ` Baolin Wang
2025-02-26 15:46 ` Brian Geffon
2025-02-26 16:23 ` [PATCH v2] " Brian Geffon
2025-02-27 7:34 ` Baolin Wang
2025-02-27 16:47 ` Brian Geffon [this message]
2025-02-27 13:32 ` [PATCH v3] " Brian Geffon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADyq12zgFigdBHiCv=AkZNLfbrmnCe2AVVOkjxNy9PwvJZsETQ@mail.gmail.com' \
--to=bgeffon@google.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mmaslanka@google.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox