linux-kernel - Re: Commit cb83b62 fails to boot with a divide by zero error.

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:	Fri, 11 May 2012 16:33:10 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Robin Holt <holt@....com>
Cc:	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: Commit cb83b62 fails to boot with a divide by zero error.

On Fri, 2012-05-11 at 08:39 -0500, Robin Holt wrote:

> We found that reverting the commit:
> cb83b62 (x86/sched/core) sched/numa: Rewrite the CONFIG_NUMA sched domain support
> 
> also got things working.

there's a particularly stupid bug in that code



---
Subject: sched, numa: Fix the new NUMA topology bits
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Date: Fri May 11 00:56:20 CEST 2012

There's no need to convert a node number to a node number by
pretending its a cpu number..

Reported-by: Yinghai Lu <yinghai@...nel.org>
Reported-and-Tested-by: Greg Pearson <greg.pearson@...com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
---
 kernel/sched/core.c |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -6378,8 +6378,7 @@ static void sched_init_numa(void)
 			sched_domains_numa_masks[i][j] = mask;
 
 			for (k = 0; k < nr_node_ids; k++) {
-				if (node_distance(cpu_to_node(j), k) >
-						sched_domains_numa_distance[i])
+				if (node_distance(j, k) > sched_domains_numa_distance[i])
 					continue;
 
 				cpumask_or(mask, mask, cpumask_of_node(k));

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