linux-kernel - Re: [PATCH] x86: clean up setup_clear/force_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:	Sat, 27 Dec 2008 12:49:09 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Rusty Russell <rusty@...tcorp.com.au>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: clean up setup_clear/force_cpu_cap handling

Ingo Molnar wrote:
> * Yinghai Lu <yinghai@...nel.org> wrote:
> 
>> Impact: fix and cleanup
>>
>> setup_force_cpu_cap() only have one user xen
>> but it should not reuse cleared_cpu_cpus. it will have problem
>> for smp.
>>
>> need to have cpu_cpus_set array too.
>> also need to setup handling before all cpus cap AND
>>
>> Signed-off-by: Yinghai Lu <yinghai.lu@...nel.org>
>>
>> ---
>>  arch/x86/include/asm/cpufeature.h |    4 ++--
>>  arch/x86/include/asm/processor.h  |    3 ++-
>>  arch/x86/kernel/cpu/common.c      |   17 ++++++++++++-----
>>  3 files changed, 16 insertions(+), 8 deletions(-)
> 
> Rusty, you'll carry this patch in your linux-2.6-boot-params.git tree, 
> right? Merging this in the x86 tree would just needlessly complicate your 
> logistics, right?

Rusty polished this patch a little bit and put the updated one in his tree.
so you may need to pick up the updated one.

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