From: Alistair Popple <apopple@nvidia.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, osalvador@suse.de,
jgg@ziepe.ca, jhubbard@nvidia.com, peterx@redhat.com,
linux-kernel@vger.kernel.org, dan.j.williams@intel.com
Subject: Re: [PATCH 1/2] mm/gup: Remove dead pgmap refcounting code
Date: Wed, 3 Sep 2025 08:52:05 +1000 [thread overview]
Message-ID: <zpp2ztak5c5e5kies6er4mioolsjpufxgizcrjf2erk4fxryox@dvnbkls725wu> (raw)
In-Reply-To: <ee3ee18c-27a0-4c38-a639-e93e91a392ad@redhat.com>
On 2025-09-02 at 17:46 +1000, David Hildenbrand <david@redhat.com> wrote...
> On 02.09.25 07:14, Alistair Popple wrote:
> > Prior to aed877c2b425 ("device/dax: properly refcount device dax pages
>
> "to commit aed877c2b425" ...
>
> > when mapping") ZONE_DEVICE pages were not fully reference counted when
> > mapped into user page tables. Instead GUP would take a reference on the
> > associated pgmap to ensure the results of pfn_to_page() remained valid.
> >
> > This is no longer required and most of the code was removed by
> > fd2825b0760a ("mm/gup: remove pXX_devmap usage from get_user_pages()").
>
> "by commit fd2825b0760a"
>
> Otherwise checkpatch complains.
Aha! Clearly I was tired ... I saw the checkpatch spew but couldn't figure out
what it was trying to tell me other than I was wrong :).
Anyway the kernel test bot tells me I missed a call site so will fix both these
issues and respin. Thanks!
> > Finish cleaning this up by removing the dead calls to put_dev_pagemap()
> > and the temporary context struct.
>
> [...]
>
> > {
> > @@ -661,7 +656,7 @@ static inline bool can_follow_write_pud(pud_t pud, struct page *page,
> > static struct page *follow_huge_pud(struct vm_area_struct *vma,
> > unsigned long addr, pud_t *pudp,
> > - int flags, struct follow_page_context *ctx)
> > + int flags, unsigned long *page_mask)
> > {
> > struct mm_struct *mm = vma->vm_mm;
> > struct page *page;
> > @@ -688,7 +683,7 @@ static struct page *follow_huge_pud(struct vm_area_struct *vma,
> > if (ret)
> > page = ERR_PTR(ret);
> > else
> > - ctx->page_mask = HPAGE_PUD_NR - 1;
> > + *page_mask = HPAGE_PUD_NR - 1;
>
> At some point we should remove that page_mask thingy as well and handle it
> like gup-fast: let follow_* will in the array directly.
>
>
> Lovely
>
> Acked-by: David Hildenbrand <david@redhat.com>
>
> --
> Cheers
>
> David / dhildenb
>
next prev parent reply other threads:[~2025-09-02 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 5:14 Alistair Popple
2025-09-02 5:14 ` [PATCH 2/2] mm/memremap: Remove unused get_dev_pagemap() parameter Alistair Popple
2025-09-02 7:47 ` David Hildenbrand
2025-09-02 12:06 ` Jason Gunthorpe
2025-09-02 20:31 ` kernel test robot
2025-09-03 1:20 ` dan.j.williams
2025-09-02 7:46 ` [PATCH 1/2] mm/gup: Remove dead pgmap refcounting code David Hildenbrand
2025-09-02 22:52 ` Alistair Popple [this message]
2025-09-02 12:06 ` Jason Gunthorpe
2025-09-03 23:07 ` Alistair Popple
2025-09-03 1:17 ` dan.j.williams
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=zpp2ztak5c5e5kies6er4mioolsjpufxgizcrjf2erk4fxryox@dvnbkls725wu \
--to=apopple@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--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