[PATCH 1/1 v9] use crc32 instead of md5 for hibernation e820 integrity check

Hibernation fails on a system in fips mode because md5 is used for the e820 integrity check and is not available. Use crc32 instead. The check is intended to detect whether the E820 memory map provided by the firmware after cold boot unexpectedly differs from the one that was in use when the hiber

RE: [PATCH 1/1 v9] use crc32 instead of md5 for hibernation e820 integrity check

> From: Chris von Recklinghausen > Sent: Friday, April 16, 2021 6:17 AM > ... > Hibernation fails on a system in fips mode because md5 is used for the e820 > integrity check and is not available. Use crc32 instead. > > The check is intended to detect whether the E820 memory map provided > by the

Re: [PATCH 1/1 v9] use crc32 instead of md5 for hibernation e820 integrity check

On Fri, Apr 16, 2021 at 09:16:55AM -0400, Chris von Recklinghausen wrote: > Hibernation fails on a system in fips mode because md5 is used for the e820 > integrity check and is not available. Use crc32 instead. Doesn't the commit title need to be prefixed with something like "x86/power"? > The ch

[PATCH 1/1 v9] use crc32 instead of md5 for hibernation e820 integrity check

Hibernation fails on a system in fips mode because md5 is used for the e820 integrity check and is not available. Use crc32 instead. The check is intended to detect whether the E820 memory map provided by the firmware after cold boot unexpectedly differs from the one that was in use when the hiber