linux-kernel - Re: [PATCH] x86: Fix override new_cpu

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]

Date:	Wed, 26 Jun 2013 18:56:52 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Wang YanQing <udknight@...il.com>
Cc:	hpa@...or.com, tglx@...utronix.de, mingo@...hat.com,
	x86@...nel.org, bp@...e.de, fenghua.yu@...el.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Fix override new_cpu_data.x86 with 486

On Thu, Jun 27, 2013 at 12:26:40AM +0800, Wang YanQing wrote:
> 
> We should set X86 to 486 before use cpuid
> to detect the cpu type, if we set X86 to 486
> after cpuid, then we will get 486 for ever.

Yep, that should be fixed, AFAICT. But it is too late for me in the day
to actually stare at asm and not miss anything so I'd need a doublecheck
from hpa.

> Yes, we will correct this in early_cpu_init,
> but it is still a wrong behavior, right? So
> just fix it.
> 
> I also find maybe we can delete the new_cpu_data,
> because we will over write all the information
> in early_cpu_init, and before early_cpu_init,
> there is no user of new_cpu_data, but this is
> another patch in the future.

That won't be that simple because reportedly there are cpus which report
different CPUID levels due to wrong MSR programming.

And, even if you went and removed it, you'd need to test your patch on
everything so that you can make sure you don't break anything. Which is
not worth the trouble, IMHO.

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/