From: "Michał Cłapiński" <mclapinski@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
kexec@lists.infradead.org, linux-mm@kvack.org
Cc: Evangelos Petrongonas <epetron@amazon.de>,
Mike Rapoport <rppt@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
Alexander Graf <graf@amazon.com>,
linux-kernel@vger.kernel.org,
Pasha Tatashin <pasha.tatashin@soleen.com>
Subject: Re: [PATCH v3] kho: add support for deferred struct page init
Date: Thu, 12 Feb 2026 14:26:39 +0100 [thread overview]
Message-ID: <CAAi7L5d19R8ftDsvwJpoxjkx9YSVkBuANOAixk75P98KJU=r4g@mail.gmail.com> (raw)
In-Reply-To: <CA+CK2bBfJDD5SPJqwCaGbaGZe9FncONMsck0QkOb8WwmDSh_Yg@mail.gmail.com>
On Wed, Feb 11, 2026 at 8:40 PM Pasha Tatashin
<pasha.tatashin@soleen.com> wrote:
>
> On Wed, Feb 11, 2026 at 12:40 PM Michal Clapinski <mclapinski@google.com> wrote:
> >
> > From: Evangelos Petrongonas <epetron@amazon.de>
> >
> > When CONFIG_DEFERRED_STRUCT_PAGE_INIT is enabled, struct page
> > initialization is deferred to parallel kthreads that run later
> > in the boot process.
> >
> > During KHO restoration, deserialize_bitmap() writes metadata for
> > each preserved memory region. However, if the struct page has not been
> > initialized, this write targets uninitialized memory, potentially
> > leading to errors like:
> > BUG: unable to handle page fault for address: ...
> >
> > Fix this by introducing kho_get_preserved_page(), which ensures
> > all struct pages in a preserved region are initialized by calling
> > init_deferred_page() which is a no-op when deferred init is disabled
> > or when the struct page is already initialized.
> >
>
> Co-developed-by: Michal Clapinski <mclapinski@google.com>
>
> > Signed-off-by: Evangelos Petrongonas <epetron@amazon.de>
> > Signed-off-by: Michal Clapinski <mclapinski@google.com>
> > Reviewed-by: Pratyush Yadav (Google) <pratyush@kernel.org>
> > ---
> > v3:
> > - changed commit msg
> > - don't invoke early_pfn_to_nid if CONFIG_DEFERRED_STRUCT_PAGE_INIT=n
>
> Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Hello Andrew,
could you please apply this with the added Co-developed-by tag?
Thanks,
Michal
next prev parent reply other threads:[~2026-02-12 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 17:39 Michal Clapinski
2026-02-11 19:40 ` Pasha Tatashin
2026-02-12 13:26 ` Michał Cłapiński [this message]
2026-02-12 11:41 ` Mike Rapoport
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='CAAi7L5d19R8ftDsvwJpoxjkx9YSVkBuANOAixk75P98KJU=r4g@mail.gmail.com' \
--to=mclapinski@google.com \
--cc=akpm@linux-foundation.org \
--cc=epetron@amazon.de \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.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