linux-kernel - Re: patch/option to wipe memory at boot?

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]

Message-ID: <46F16ADC.3030307@redhat.com>
Date:	Wed, 19 Sep 2007 14:30:52 -0400
From:	Chris Snook <csnook@...hat.com>
To:	David Madore <david.madore@....fr>
CC:	linux-kernel@...r.kernel.org, Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: patch/option to wipe memory at boot?

David Madore wrote:
> On Mon, Sep 17, 2007 at 11:11:52AM -0700, Jeremy Fitzhardinge wrote:
>> Boot memtest86 for a little while before booting the kernel?  And if you
>> haven't already run it for a while, then that would be your first step
>> anyway.
> 
> Indeed, that does the trick, thanks for the suggestion.  So I can be
> quite confident, now, that my RAM is sane and it's just that the BIOS
> doesn't initialize it properly.
> 
> But I'd still like some way of filling the RAM when Linux starts (or
> perhaps in the bootloader), because letting memtest86 run after every
> cold reboot isn't a very satisfactory solution.

Bootloaders like to do things like run in 16-bit or 32-bit mode on boxes where 
higher bitness is necessary to access all the memory.  It may be possible to do 
this in the bootloader, but the BIOS is clearly the correct place to fix this 
problem.

	-- Chris
-
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/