From: Pratyush Yadav <pratyush@kernel.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: Michal Clapinski <mclapinski@google.com>,
Evangelos Petrongonas <epetron@amazon.de>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Mike Rapoport <rppt@kernel.org>,
Alexander Graf <graf@amazon.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] kho: add support for deferred struct page init
Date: Tue, 10 Feb 2026 15:00:22 +0100 [thread overview]
Message-ID: <2vxza4xgsnpl.fsf@kernel.org> (raw)
In-Reply-To: <2vxzecmssnxx.fsf@kernel.org> (Pratyush Yadav's message of "Tue, 10 Feb 2026 14:55:22 +0100")
On Tue, Feb 10 2026, Pratyush Yadav wrote:
> On Tue, Feb 10 2026, Michal Clapinski wrote:
>
>> 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.
>>
>> Signed-off-by: Evangelos Petrongonas <epetron@amazon.de>
>> Signed-off-by: Michal Clapinski <mclapinski@google.com>
>
> Reviewed-by: Pratyush Yadav (Google) <pratyush@kernel.org>
Wait. I just noticed that Michal took authorship of the patch. I talked
to him and he said that was by mistake.
Andrew, can you please give the authorship to Evangelos when you queue
the patch?
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2026-02-10 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 13:04 Michal Clapinski
2026-02-10 13:55 ` Pratyush Yadav
2026-02-10 14:00 ` Pratyush Yadav [this message]
2026-02-10 15:09 ` 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=2vxza4xgsnpl.fsf@kernel.org \
--to=pratyush@kernel.org \
--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=mclapinski@google.com \
--cc=pasha.tatashin@soleen.com \
--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