From: Mike Rapoport <rppt@kernel.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Subject: Re: [PATCH] secretmem: Remove uses of struct page
Date: Sun, 15 Jun 2025 10:10:30 +0300 [thread overview]
Message-ID: <aE5x5mY5b1ecbBIZ@kernel.org> (raw)
In-Reply-To: <20250613194744.3175157-1-willy@infradead.org>
On Fri, Jun 13, 2025 at 08:47:43PM +0100, Matthew Wilcox (Oracle) wrote:
> Use filemap_lock_folio() instead of find_lock_page() to retrieve
> a folio from the page cache.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> mm/secretmem.c | 16 +++++++---------
> 1 file changed, 7 insertions(+), 9 deletions(-)
>
> diff --git a/mm/secretmem.c b/mm/secretmem.c
> index 589b26c2d553..dfa8d8d10bcb 100644
> --- a/mm/secretmem.c
> +++ b/mm/secretmem.c
> @@ -54,7 +54,6 @@ static vm_fault_t secretmem_fault(struct vm_fault *vmf)
> pgoff_t offset = vmf->pgoff;
> gfp_t gfp = vmf->gfp_mask;
> unsigned long addr;
> - struct page *page;
> struct folio *folio;
> vm_fault_t ret;
> int err;
> @@ -65,16 +64,15 @@ static vm_fault_t secretmem_fault(struct vm_fault *vmf)
> filemap_invalidate_lock_shared(mapping);
>
> retry:
> - page = find_lock_page(mapping, offset);
> - if (!page) {
> + folio = filemap_lock_folio(mapping, offset);
> + if (!folio) {
> folio = folio_alloc(gfp | __GFP_ZERO, 0);
> if (!folio) {
> ret = VM_FAULT_OOM;
> goto out;
> }
>
> - page = &folio->page;
> - err = set_direct_map_invalid_noflush(page);
> + err = set_direct_map_invalid_noflush(folio_page(folio, 0));
> if (err) {
> folio_put(folio);
> ret = vmf_error(err);
> @@ -90,7 +88,7 @@ static vm_fault_t secretmem_fault(struct vm_fault *vmf)
> * already happened when we marked the page invalid
> * which guarantees that this call won't fail
> */
> - set_direct_map_default_noflush(page);
> + set_direct_map_default_noflush(folio_page(folio, 0));
> if (err == -EEXIST)
> goto retry;
>
> @@ -98,11 +96,11 @@ static vm_fault_t secretmem_fault(struct vm_fault *vmf)
> goto out;
> }
>
> - addr = (unsigned long)page_address(page);
> + addr = (unsigned long)folio_address(folio);
> flush_tlb_kernel_range(addr, addr + PAGE_SIZE);
> }
>
> - vmf->page = page;
> + vmf->page = folio_file_page(folio, vmf->pgoff);
> ret = VM_FAULT_LOCKED;
>
> out:
> @@ -154,7 +152,7 @@ static int secretmem_migrate_folio(struct address_space *mapping,
>
> static void secretmem_free_folio(struct folio *folio)
> {
> - set_direct_map_default_noflush(&folio->page);
> + set_direct_map_default_noflush(folio_page(folio, 0));
> folio_zero_segment(folio, 0, folio_size(folio));
> }
>
> --
> 2.47.2
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-06-15 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 19:47 [PATCH] secretmem: Remove uses of struct page Matthew Wilcox (Oracle)
2025-06-15 7:10 ` Mike Rapoport [this message]
2025-06-16 13:56 ` Lorenzo Stoakes
2025-06-16 21:19 ` David Hildenbrand
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=aE5x5mY5b1ecbBIZ@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).