linux-kernel - cpu_mask_to_apicid: Not a valid mask! [was: x86_32: summit_32, use BAD

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] [day] [month] [year] [list]

Message-ID: <49B77A42.5060106@gmail.com>
Date:	Wed, 11 Mar 2009 09:45:54 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	x86@...nel.org, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, yinghai@...nel.org,
	andi@...stfloor.org
Subject: cpu_mask_to_apicid: Not a valid mask! [was: x86_32: summit_32, use
 BAD_APICID]

Adding Yinghai and Andi to CCs, maybe they can help? And changing subject.

On 8.3.2009 18:00, Jiri Slaby wrote:
> On 28.2.2009 09:21, Ingo Molnar wrote:
>>> I've sent 4 more patches, but there are still issues:
>>> * es7000 + summit: I haven't solved calling with all bits set (only all
>>> online is sufficient to trigger this). Some of the processors needn't be
>>> on the same apic cluster. It will scream now (again -- it did before
>>> adding the "optimisation"). Actually I don't know how to solve this. How
>>> the caller would know the correct mask, ANDing with a apic->target_cpus
>>> retval?
>
> Anybody, please? This is not a theoretical issue, this is a real problem
> we hit...
--
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/