linux-kernel - Re: [REGRESSION] Kernel booted via kexec fails to resume from hibernation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z4ZkU81xJwEUiCbV@desktop0a>
Date: Tue, 14 Jan 2025 14:19:15 +0100
From: Roberto Ricci <io@...icci.it>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: ebiederm@...ssion.com, rafael@...nel.org, pavel@....cz,
	ytcoode@...il.com, kexec@...ts.infradead.org,
	linux-pm@...r.kernel.org, regressions@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [REGRESSION] Kernel booted via kexec fails to resume from
 hibernation

On 2025-01-13 Mon 15:17:49 -0800, Andrew Morton wrote:
> Thanks.  Are you able to confirm that reverting 18d565ea95fe fixes things?

Actually no, reverting 18d565ea95fe553f442c5bbc5050415bab3c3fa4
("kexec_file: fix incorrect temp_start value in locate_mem_hole_top_down()")
on top of v6.13-rc7 does not fix the issue.
So this might not be the real culprit.
But I verified that 18d565ea95fe553f442c5bbc5050415bab3c3fa4 is affected
while 18d565ea95fe553f442c5bbc5050415bab3c3fa4~1 is not.