linux-kernel - Re: [PATCH] i386/bigsmp: eliminate false warnings regarding logical APIC ID mismatches

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: <4E81AC2B0200007800057F62@nat28.tlf.novell.com>
Date:	Tue, 27 Sep 2011 09:57:47 +0100
From:	"Jan Beulich" <JBeulich@...e.com>
To:	"Konrad Rzeszutek Wilk" <konrad.wilk@...cle.com>
Cc:	<mingo@...e.hu>, "Stratos Psomadakis" <psomas@...too.org>,
	<stable@...nel.org>, <tj@...nel.org>, <tglx@...utronix.de>,
	<linux-kernel@...r.kernel.org>, <hpa@...or.com>
Subject: Re: [PATCH] i386/bigsmp: eliminate false warnings regarding
	 logical APIC ID mismatches

>>> On 26.09.11 at 18:13, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> wrote:
>> >> --- 3.1-rc2/arch/x86/kernel/apic/probe_32.c
>> >> +++ 3.1-rc2-i386-bigsmp-early-lapicid-override/arch/x86/kernel/apic/probe_32.c
>> >> @@ -203,7 +203,18 @@ void __init default_setup_apic_routing(v
>> >>  	if (!cmdline_apic && apic == &apic_default) {
>> >>  		struct apic *bigsmp = generic_bigsmp_probe();
>> >>  		if (bigsmp) {
>> >> +			unsigned int cpu;
>> >> +
>> >>  			apic = bigsmp;
>> >> +			for_each_possible_cpu(cpu) {
>> >> +				if (early_per_cpu(x86_cpu_to_logical_apicid,
>> >> +						  cpu) == BAD_APICID)
>> >> +					continue;
>> >> +				early_per_cpu(x86_cpu_to_logical_apicid,
>> >> +					      cpu) =
>> >> +					bigsmp->x86_32_early_logical_apicid
>> >> +						(cpu);
>> >> +			}
>> >>  			printk(KERN_INFO "Overriding APIC driver with %s\n",
>> >>  			       apic->name);
>> >>  		}
>> > Will this patch be included in 3.1 (so that it gets merged in 3.0-stable
>> > kernels sooner too) or will it go for 3.2?
>> 
>> That can only be answered by the maintainers (on Cc), not me - afaict
>> it didn't even get applied to -tip yet.
> 
> ping?

I haven't seen any tipbot for it (despite having re-sent it about two
weeks ago), so I have to assume it still didn't go in. I also didn't see
anything else (e.g. reasons why this shouldn't get applied), just
complete silence (I would almost say as "usual", no matter how hard
I try to meet Ingo's expectations on patch descriptions).

So I can only again defer answering your question to the maintainers,
who are all on Cc.

Jan

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