linux-kernel - Re: [PATCH 1/1] irqchip/gicv3: iterate over possible CPUs by for_each_possible

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]

Date:   Fri, 15 Sep 2017 15:42:27 +0100
From:   Marc Zyngier <marc.zyngier@....com>
To:     zijun_hu <zijun_hu@...o.com>
Cc:     <linux-kernel@...r.kernel.org>, <zijun_hu@....com>,
        <tglx@...utronix.de>, <jason@...edaemon.net>,
        <james.morse@....com>, <sudeep.holla@....com>
Subject: Re: [PATCH 1/1] irqchip/gicv3: iterate over possible CPUs by for_each_possible_cpu()

On Fri, Sep 15 2017 at 11:05:25 am BST, zijun_hu <zijun_hu@...o.com> wrote:
> On 09/15/2017 03:20 AM, Marc Zyngier wrote:
>> On Thu, Sep 14 2017 at  1:15:14 pm BST, zijun_hu <zijun_hu@...o.com> wrote:
>>> From: zijun_hu <zijun_hu@....com>
>>>
>>> get_cpu_number() doesn't use existing helper to iterate over possible
>>> CPUs, so error happens in case of discontinuous @cpu_possible_mask
>>> such as 0b11110001.
>> 
>> Do you have an example of such a situation? Your patch is definitely an
>> improvement, but I'd like to understand how you get there...
>> 
>> Thanks,
>> 
>> 	M.
>> 
> a few conditions which maybe result in discontiguous @cpu_possible_mask
> are noticed and considered of by ARM64 init code as indicated by bellow code
> segments:
> in arch/arm64/kernel/smp.c :
> void __init smp_init_cpus(void) {
> ......
> 	/*
> 	 * We need to set the cpu_logical_map entries before enabling
> 	 * the cpus so that cpu processor description entries (DT cpu nodes
> 	 * and ACPI MADT entries) can be retrieved by matching the cpu hwid
> 	 * with entries in cpu_logical_map while initializing the cpus.
> 	 * If the cpu set-up fails, invalidate the cpu_logical_map entry.
> 	 */
> 	for (i = 1; i < nr_cpu_ids; i++) {
> 		if (cpu_logical_map(i) != INVALID_HWID) {
> 			if (smp_cpu_setup(i))
> 				cpu_logical_map(i) = INVALID_HWID;
> 		}
> 	}

Right. It is not so much that the CPU doesn't exist as I initially
thought (and couldn't really believe that it could happen), but rather
that the CPU may have failed to come up (which is slightly more likely).

Well spotted. Would you mind respinning it with a commit message that
outlines the condition under which this can happen? I'll the take it as
a fix post -rc1.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny.