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] [day] [month] [year] [list]
Date:	Fri, 21 Mar 2014 01:37:51 -0700 (PDT)
From:	ivory <ich7@...-topmail.de>
To:	linux-kernel@...r.kernel.org
Subject: Re: [tip:x86/mm] x86, mm: Move reserving low memory later in
 initialization

This patch seems to make the bios_corruption_check not to cover the lowest
64kB of memory anymore but only the lowest 4kB. Was this deliberate?
When I use kernel 3.9 or higher I always get low mem corruption message from
the bios corruption checker when I resume from suspend.

Below kernel 3.9 I see this boot message:
e820 update range: 0000000000000000 - 0000000000010000 (usable) ==>
(reserved)
... which is the 64kB.

But on newer kernels the message changed to:
e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
... which is only 4kB.

The corrupted low mem areas I get the message for after resuming from
suspend is this:
 Corrupted low memory at c0002d00 (2d00 phys) = 11060000
 Corrupted low memory at c0002d04 (2d04 phys) = 80805122
 Corrupted low memory at c0002d08 (2d08 phys) = 00860003

How to fix this in kernel 3.9 and higher?

Thanks for your help and best regards.



--
View this message in context: http://linux-kernel.2935.n7.nabble.com/tip-x86-mm-x86-mm-Move-reserving-low-memory-later-in-initialization-tp601280p827938.html
Sent from the Linux Kernel mailing list archive at Nabble.com.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ