linux-kernel - Re: [PATCH 20/20] x86_64: Move CPU verification code to common file

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

Message-ID: <20061118063802.GE30547@bingen.suse.de>
Date:	Sat, 18 Nov 2006 07:38:02 +0100
From:	Andi Kleen <ak@...e.de>
To:	LKML <linux-kernel@...r.kernel.org>, olecom@...wer.upol.cz,
	vgoyal@...ibm.com, akpm@...l.org, rjw@...k.pl,
	ebiederm@...ssion.com, hpa@...or.com,
	Reloc Kernel List <fastboot@...ts.osdl.org>, pavel@...e.cz,
	magnus.damm@...il.com, ak@...e.de
Subject: Re: [PATCH 20/20] x86_64: Move CPU verification code to common file

> May hang be done optional? There was a discussion about applying
> "panic" reboot timeout here. Is it possible to implement somehow?

It would be tricky, but might be possible.  But that would be a completely
new feature -- the kernel has always hung in this case. If you think you need 
it submit a (followup) patch. But I don't think it's fair to ask Vivek to do it.

Besides i don't think it would be any useful. panic reboot only
makes sense if you can recover after reboot. But if your CPU somehow
suddenly loses its ability to run 64bit code, no reboot of the world will 
recover.

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