linux-kernel - Re: [PATCH] [9/20] x86: Don't use oops

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: <200801031352.42111.ak@suse.de>
Date:	Thu, 3 Jan 2008 13:52:42 +0100
From:	Andi Kleen <ak@...e.de>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [9/20] x86: Don't use oops_begin in 64bit mce code

On Thursday 03 January 2008 11:39:12 Ingo Molnar wrote:
> 
> * Andi Kleen <ak@...e.de> wrote:
> 
> > It is not really useful to lock machine checks against oopses. And 
> > machine checks normally don't nest, so they don't need their own 
> > locking. Just call bust_spinlock/console_verbose directly.
> 
> is this in response to any particular incident you've seen?


No, that was a preparatory patch for the "use 64bit machine check code
for 32bit kernels" because 32bit doesn't have oops_begin(), but it is
useful on its own.

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