[dpdk-dev] [PATCH v2] bonding: 8023ad: fix incorrect typecast of socket

2015-08-10 Thread Thomas Monjalon
> > 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. > > > > Signed-off-by: Sergey Balabanov > > Acked-by: Pablo

[dpdk-dev] [PATCH v2] bonding: 8023ad: fix incorrect typecast of socket

2015-08-07 Thread Sergey Balabanov
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. Signed-off-by: Sergey Balabanov ---

[dpdk-dev] [PATCH v2] bonding: 8023ad: fix incorrect typecast of socket

2015-08-07 Thread De Lara Guarch, Pablo
> -Original Message- > From: Sergey Balabanov [mailto:balabanovsv at ecotelecom.ru] > Sent: Friday, August 07, 2015 10:33 AM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo; Sergey Balabanov > Subject: [PATCH v2] bonding: 8023ad: fix incorrect typecast of socket > > On slave