From 85cc012ddda48ee6930789187bbfb661066e1c02 Mon Sep 17 00:00:00 2001 From: Sergey Balabanov Date: Fri, 7 Aug 2015 12:33:18 +0300 Subject: [PATCH] bonding: fix socket id for LACP slave On slave activation in LACP (8023AD) SOCKET_ANY_ID (which is -1) is being casted to unsigned char and then to signed int. The result is that socket_id has value of 255, not -1. This results to memory allocation failure. Fixes: 46fb43683679 ("bond: add mode 4") Signed-off-by: Sergey Balabanov Acked-by: Pablo de Lara --- drivers/net/bonding/rte_eth_bond_8023ad.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/bonding/rte_eth_bond_8023ad.c b/drivers/net/bonding/rte_eth_bond_8023ad.c index 97a828e7e6..c0f0b99199 100644 --- a/drivers/net/bonding/rte_eth_bond_8023ad.c +++ b/drivers/net/bonding/rte_eth_bond_8023ad.c @@ -849,7 +849,7 @@ bond_mode_8023ad_activate_slave(struct rte_eth_dev *bond_dev, uint8_t slave_id) }; char mem_name[RTE_ETH_NAME_MAX_LEN]; - uint8_t socket_id; + int socket_id; unsigned element_size; /* Given slave mus not be in active list */ -- 2.20.1