linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] mm: Fix memblock_free_late() when using deferred struct page
Date: Wed, 4 Feb 2026 09:39:59 +0200	[thread overview]
Message-ID: <aYL3zxuTLT8N7C8-@kernel.org> (raw)
In-Reply-To: <279931074239b7f3812c4cb3969f887303c8cc26.camel@kernel.crashing.org>

On Wed, Feb 04, 2026 at 06:53:29AM +1100, Benjamin Herrenschmidt wrote:
> On Tue, 2026-02-03 at 20:40 +0200, Mike Rapoport wrote:
> > >  void __init memblock_free_pages(struct page *page, unsigned long pfn,
> > > -							unsigned int
> > > order)
> > > +				unsigned int order, bool reserved)
> > 
> > I've been thinking about after more coffee after our chat on IRC, and I
> > believe we don't need the bool reserved here.
> > 
> > Since the assumption that memblock_free_late() should be called only after
> > buddy is initialized, all the reserved pages should have their memmap setup
> > with PG_Reserved set. So we can use PageReserved() instead of passing the
> > boolean.
> 
> What about free_low_memory_core_early() -> 
>              __free_memory_core() ->
>                __free_pages_memory() ->
>                  memblock_free_pages() ?
> 
> I might be missing something but I don't see what would restrict this
> to the early pre-initialized struct pages other than that
> early_page_initialised() test, so we can't rely on anything in struct
> page inside memblock_free_pages().

Right, we can't rely on PG_Reserved being cleared for uninitialized pages :/

But I overlooked an easier and actually reliable way: use
free_reserved_area() instead of memblock_free_late().

> Cheers,
> Ben.

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2026-02-04  7:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03  8:02 Benjamin Herrenschmidt
2026-02-03 18:40 ` Mike Rapoport
2026-02-03 19:53   ` Benjamin Herrenschmidt
2026-02-04  7:39     ` Mike Rapoport [this message]
2026-02-04  9:02       ` Benjamin Herrenschmidt
2026-02-06 10:33         ` Mike Rapoport
2026-02-10  1:04           ` Benjamin Herrenschmidt
2026-02-10  2:10             ` Benjamin Herrenschmidt
2026-02-10  6:17               ` Benjamin Herrenschmidt
2026-02-10  8:34                 ` Benjamin Herrenschmidt
2026-02-10 14:32                   ` Mike Rapoport
2026-02-10 23:23                     ` Benjamin Herrenschmidt
2026-02-11  5:20                       ` Mike Rapoport
2026-02-16  5:34                       ` Benjamin Herrenschmidt
2026-02-16  6:51                         ` Benjamin Herrenschmidt
2026-02-16  4:53                     ` Benjamin Herrenschmidt
2026-02-16 15:28                       ` Mike Rapoport
2026-02-16 10:36           ` Alexander Potapenko
2026-02-17  8:28 ` [PATCH v2] " Benjamin Herrenschmidt
2026-02-17 12:32   ` Mike Rapoport
2026-02-17 22:00     ` Benjamin Herrenschmidt
2026-02-17 21:47   ` Benjamin Herrenschmidt
2026-02-18  0:15     ` Benjamin Herrenschmidt
2026-02-18  8:05       ` Mike Rapoport
2026-02-19  2:48         ` Benjamin Herrenschmidt
2026-02-19 10:16           ` Mike Rapoport
2026-02-19 22:46             ` Benjamin Herrenschmidt
2026-02-20  4:57               ` Benjamin Herrenschmidt
2026-02-20  9:09                 ` Mike Rapoport
2026-02-20  9:00               ` Mike Rapoport
2026-02-20  5:12             ` Benjamin Herrenschmidt
2026-02-20  5:15             ` Benjamin Herrenschmidt
2026-02-20  5:47             ` Benjamin Herrenschmidt

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=aYL3zxuTLT8N7C8-@kernel.org \
    --to=rppt@kernel.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-mm@kvack.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