linux-kernel - Re: [PATCH] x86: fdiv bug detection fix

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: <20080731215712.GC23801@elte.hu>
Date:	Thu, 31 Jul 2008 23:57:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Krzysztof Helt <krzysztof.h1@...pl>
Cc:	hpa@...or.com, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] x86: fdiv bug detection fix


* Krzysztof Helt <krzysztof.h1@...pl> wrote:

> From: Krzysztof Helt <krzysztof.h1@...pl>
> 
> The fdiv detection code writes s32 integer into
> the boot_cpu_data.fdiv_bug. 
> However, the boot_cpu_data.fdiv_bug is only char (s8)
> field so the detection overwrites already set fields for
> other bugs, e.g. the f00f bug field.
> 
> Use local s32 variable to receive result.

applied to tip/x86/urgent, thanks Krzysztof!

this bug seems to be rather old - i guess new kernels rarely get tested 
with those CPUs that are affected by those bugs?

	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/