From: Kees Cook <kees@kernel.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Harry (Hyeonggon) Yoo" <42.hyeyoo@gmail.com>,
Huacai Chen <chenhuacai@loongson.cn>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Pavel Machek <pavel@kernel.org>,
linux-pm@vger.kernel.org, GONG Ruiqi <gongruiqi@huaweicloud.com>,
Xiu Jianfeng <xiujianfeng@huawei.com>,
stable@vger.kernel.org, Yuli Wang <wangyuli@uniontech.com>,
Vlastimil Babka <vbabka@suse.cz>,
Christoph Lameter <cl@linux.com>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Pekka Enberg <penberg@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
GONG Ruiqi <gongruiqi1@huawei.com>
Subject: Re: How does swsusp work with randomization features? (was: mm/slab: Initialise random_kmalloc_seed after initcalls)
Date: Tue, 25 Feb 2025 12:41:12 -0800 [thread overview]
Message-ID: <202502251240.49E8674AD@keescook> (raw)
In-Reply-To: <CAAhV-H5UaEbA0DrAUfROJoiatwrjsge4DNcVTJi=8vtk2Zn+tQ@mail.gmail.com>
On Tue, Feb 25, 2025 at 07:35:13PM +0800, Huacai Chen wrote:
> I have investigated deeper, and then found it is an arch-specific
> problem (at least for LoongArch), and the correct solution is here:
> https://lore.kernel.org/loongarch/20250225111812.3065545-1-chenhuacai@loongson.cn/T/#u
Ah-ha, so it seems like some system start was being incorrectly shared
between restoration image and hibernated image? Yeah, that's important
to fix.
> But I don't know how to fix arm64.
Is arm64 broken in this same way?
--
Kees Cook
next prev parent reply other threads:[~2025-02-25 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 14:16 [PATCH] mm/slab: Initialise random_kmalloc_seed after initcalls Huacai Chen
2025-02-12 15:39 ` Harry (Hyeonggon) Yoo
2025-02-13 3:20 ` Huacai Chen
2025-02-14 9:33 ` How does swsusp work with randomization features? (was: mm/slab: Initialise random_kmalloc_seed after initcalls) Harry (Hyeonggon) Yoo
2025-02-14 10:02 ` Huacai Chen
2025-02-14 12:44 ` Harry (Hyeonggon) Yoo
2025-02-15 9:53 ` Huacai Chen
2025-02-15 14:05 ` Harry (Hyeonggon) Yoo
2025-02-16 5:08 ` Huacai Chen
2025-02-19 14:10 ` How does swsusp work with randomization features? Vlastimil Babka
2025-02-19 17:25 ` How does swsusp work with randomization features? (was: mm/slab: Initialise random_kmalloc_seed after initcalls) Kees Cook
2025-02-19 18:09 ` Rafael J. Wysocki
2025-02-25 11:35 ` Huacai Chen
2025-02-25 20:41 ` Kees Cook [this message]
2025-02-26 7:31 ` Huacai Chen
2025-02-27 2:50 ` ARM64 crashes when resuming from hibernation (randomization features enabled) Harry Yoo
2025-02-18 9:33 ` [PATCH] mm/slab: Initialise random_kmalloc_seed after initcalls WangYuli
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=202502251240.49E8674AD@keescook \
--to=kees@kernel.org \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=cl@linux.com \
--cc=gongruiqi1@huawei.com \
--cc=gongruiqi@huaweicloud.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=penberg@kernel.org \
--cc=rafael@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=wangyuli@uniontech.com \
--cc=xiujianfeng@huawei.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