[PATCH v2] openvswitch: allocate nr_node_ids flow_stats instead of num_possible_nodes

Pravin Shelar pshelar at nicira.com
Wed Jul 22 04:29:56 AEST 2015

On Tue, Jul 21, 2015 at 10:36 AM, Chris J Arges
<chris.j.arges at canonical.com> wrote:
> 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>


More information about the Linuxppc-dev mailing list