Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Aristeu Rozanski <aris@ruivo.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH v2 0/2] mm: gup: cleanup gup_fast call chain
Date: Thu, 27 Aug 2026 15:10:42 -0400	[thread overview]
Message-ID: <20260827191042.GN1736962@cathedrallabs.org> (raw)
In-Reply-To: <dab040ff-e495-4e7f-9932-c60b8299b89f@kernel.org>

On Thu, Aug 27, 2026 at 12:01:17PM +0200, David Hildenbrand (Arm) wrote:
> CI flagged that some test cases fail:
> 
> https://github.com/linux-mm/linux-mm/actions/runs/33031249149/job/98384037627?pr=3620
> 
> ==========================================
> ✗ memory failure test failed:
> # not ok 1 memory_failure.madv_hard.anon
> # not ok 2 memory_failure.madv_hard.clean_pagecache
> # not ok 3 memory_failure.madv_hard.dirty_pagecache
> # not ok 4 memory_failure.madv_soft.anon
> # not ok 5 memory_failure.madv_soft.clean_pagecache
> # not ok 6 memory_failure.madv_soft.dirty_pagecache
> 
> and I can reproduce locally.
> 
> They do use get_user_pages_fast(), so it checks out.
> 
> The following fixes most issues for me (there is still one failure on my machine
> but it reproduces even without your patches, so might be specific to my machine):
> 
> diff --git a/mm/gup.c b/mm/gup.c
> index 9b68242b6b602..a4036c02e2137 100644
> --- a/mm/gup.c
> +++ b/mm/gup.c
> @@ -3010,7 +3010,7 @@ static unsigned long gup_fast_pmd_range(pud_t *pudp, pud_t
> pud,
>                 unsigned long addr, unsigned long end,
>                 unsigned int flags, struct page **pages)
>  {
> -       unsigned long next, nr_pages, chunk_nr_pages;
> +       unsigned long next, nr_pages = 0, chunk_nr_pages;
>         pmd_t *pmdp;
> 
>         pmdp = pmd_offset_lockless(pudp, pud, addr);

oof. You want me to post a v3, followup, or you fixed it already?

-- 
Aristeu



  reply	other threads:[~2026-08-27 19:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  3:58 [PATCH v2 0/2] mm: gup: cleanup gup_fast call chain Aristeu Rozanski
2026-08-05  3:58 ` [PATCH v2 1/2] mm: gup: move pmd_protnone() into gup_fast_pmd_leaf() Aristeu Rozanski
2026-08-17  9:33   ` David Hildenbrand (Arm)
2026-08-05  3:58 ` [PATCH v2 2/2] mm: gup: cleanup the gup_fast_*() call chain Aristeu Rozanski
2026-08-17  9:32   ` David Hildenbrand (Arm)
2026-08-27 10:01 ` [PATCH v2 0/2] mm: gup: cleanup gup_fast " David Hildenbrand (Arm)
2026-08-27 19:10   ` Aristeu Rozanski [this message]
2026-08-27 19:16     ` David Hildenbrand (Arm)
2026-08-27 19:34       ` Aristeu Rozanski

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=20260827191042.GN1736962@cathedrallabs.org \
    --to=aris@ruivo.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=jhubbard@nvidia.com \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.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