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>] [day] [month] [year] [list]

Message-ID: <43d009740812290452l7a90de01nea3dad14cba58d85@mail.gmail.com>
Date:	Mon, 29 Dec 2008 19:52:30 +0700
From:	"Igor Podlesny" <for.poige+linux@...il.com>
To:	"Sitsofe Wheeler" <sitsofe@...oo.com>
Cc:	"Willy Tarreau" <w@....eu>, linux-kernel@...r.kernel.org
Subject: Re: > I even didn't have a backtrace.

2008/12/29 Sitsofe Wheeler <sitsofe@...oo.com>:
> Igor Podlesny wrote:
>>
>>        BTW, I wonder -- can the kernel store crash related information (if
>> any) in RAM, at certain addresses, so it can survive warm reboot and
>> get displayed "in dmesg" on the next boot?
>
> Perhaps you are thinking of kdump - http://lwn.net/Articles/108595/ ?

	Similar, but no exactly. I just thought that unlikely BIOS erases
memory content during "fast checks", so kernel diagnostic could be
left at certain addresses, probably duplicated for safety, and newly
booted kernel could check if there were something left for it in RAM.
That's simpler than kdump/kexec, the question is only whether memory
is really left intact during BIOS work, at least partly.

-- 
End of message. Next message?
--
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/