linux-next

mirror of https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git synced 2025-01-14 17:53:39 +00:00

History

Chris J Arges bac541e463 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@canonical.com>
Acked-by: Pravin B Shelar <pshelar@nicira.com>
Acked-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

2015-07-21 22:26:03 -07:00

actions.c

openvswitch: include datapath actions with sampled-packet upcall to userspace

2015-06-01 15:05:40 -07:00

datapath.c

openvswitch: include datapath actions with sampled-packet upcall to userspace

2015-06-01 15:05:40 -07:00

datapath.h

openvswitch: include datapath actions with sampled-packet upcall to userspace

2015-06-01 15:05:40 -07:00

dp_notify.c

genetlink: make multicast groups const, prevent abuse