[ovs-git] [openvswitch/ovs] cee066: datapath: Backport "openvswitch: allocate nr_node_...
GitHub
noreply at github.com
Fri Sep 18 20:41:54 UTC 2015
Branch: refs/heads/master
Home: https://github.com/openvswitch/ovs
Commit: cee06621d90f0a30b16735e40094918a38e2d010
https://github.com/openvswitch/ovs/commit/cee06621d90f0a30b16735e40094918a38e2d010
Author: Chris J Arges <chris.j.arges at canonical.com>
Date: 2015-09-18 (Fri, 18 Sep 2015)
Changed paths:
M datapath/flow_table.c
Log Message:
-----------
datapath: Backport "openvswitch: allocate nr_node_ids flow_stats instead of num_possible_nodes"
Upstream commit:
openvswitch: allocate nr_node_ids flow_stats instead of num_possible_nodes
Some architectures like POWER can have a NUMA node_possible_map that
contains sparse entries. This causes memory corruption with openvswitch
since it allocates flow_cache with a multiple of num_possible_nodes() and
assumes the node variable returned by for_each_node will index into
flow->stats[node].
Use nr_node_ids to allocate a maximal sparse array instead of
num_possible_nodes().
The crash was noticed after 3af229f2 was applied as it changed the
node_possible_map to match node_online_map on boot.
Fixes: 3af229f2071f5b5cb31664be6109561fbe19c861
Signed-off-by: Chris J Arges <chris.j.arges at canonical.com>
Acked-by: Pravin B Shelar <pshelar at nicira.com>
Acked-by: Nishanth Aravamudan <nacc at linux.vnet.ibm.com>
Signed-off-by: David S. Miller <davem at davemloft.net>
Upstream: bac541e4631(""openvswitch: allocate nr_node_ids flow_stats
instead of num_possible_nodes")
Signed-off-by: Pravin B Shelar <pshelar at nicira.com>
Acked-by: Jesse Gross <jesse at nicira.com>
More information about the git
mailing list