linux-kernel - Re: [PATCH] Fix paranoia about using BIOS quickboot mechanism.

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: <20080407082256.GA3524@elte.hu>
Date:	Mon, 7 Apr 2008 10:22:56 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alok Kataria <akataria@...are.com>
Cc:	mingo@...hat.com, tglx@...utronix.de, hpa@...or.com,
	linux-kernel@...r.kernel.org, Daniel Arai <arai@...are.com>,
	Zachary Amsden <zach@...are.com>
Subject: Re: [PATCH] Fix paranoia about using BIOS quickboot mechanism.


* Alok Kataria <akataria@...are.com> wrote:

> Make sure that we clear the "shutdown status flag" in the CMOS 
> register after each CPU is brought up.  This fixes a problem where the 
> "shutdown status flag" may remain set when a CPU is brought up after 
> booting.

btw., what problem does this result in, exactly?

> Tested on the X86 tree.

> + * Cleanup possible dangling ends...
> + */
> + smpboot_restore_warm_reset_vector();
> +
> return boot_error;
> }

patch got whitespace damaged - have a look at 
Documentation/email-clients.txt for details about how to send patches as 
in-line text. (or send the patch as an attachment - we accept x86 
patches as attachments too)

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