linux-kernel - Re: > I even didn't have a backtrace.

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: <20081229140728.GB31266@srcf.ucam.org>
Date:	Mon, 29 Dec 2008 14:07:28 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Sitsofe Wheeler <sitsofe@...oo.com>
Cc:	for.poige+linux@...il.com, Willy Tarreau <w@....eu>,
	linux-kernel@...r.kernel.org
Subject: Re: > I even didn't have a backtrace.

On Mon, Dec 29, 2008 at 12:59:57PM +0000, Sitsofe Wheeler wrote:
> Igor Podlesny wrote:
> >	Similar, but no exactly. I just thought that unlikely BIOS erases
> >memory content during "fast checks", so kernel diagnostic could be
> 
> My understanding is that the only part of the BIOS that doesn't get 
> cleared over a reboot (the hardware clock) is already being abused for 
> suspend tracing  - 
> http://mjmwired.net/kernel/Documentation/power/s2ram.txt .

That's the only part of the system that's guaranteed to persist over a 
power cycle. You probably have a little more flexibility with a warm 
reboot.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/