Re: [dpdk-dev] [PATCH v3 0/4] Enforce checking on flag values in API's

2020-06-16 Thread Thomas Monjalon
28/04/2020 12:28, Bruce Richardson: > On Mon, Apr 27, 2020 at 04:16:21PM -0700, Stephen Hemminger wrote: > > The DPDK API's are lax about checking for undefined flag values. > > This makes it impossible to add new bits to existing API's > > without causing ABI breakage. This means we end up doing u

Re: [dpdk-dev] [PATCH v3 0/4] Enforce checking on flag values in API's

2020-04-28 Thread Ananyev, Konstantin
> The DPDK API's are lax about checking for undefined flag values. > This makes it impossible to add new bits to existing API's > without causing ABI breakage. This means we end up doing unnecessary > symbol versioning just to work around applications that might > pass in naughty bits. > > This is

Re: [dpdk-dev] [PATCH v3 0/4] Enforce checking on flag values in API's

2020-04-28 Thread Bruce Richardson
On Mon, Apr 27, 2020 at 04:16:21PM -0700, Stephen Hemminger wrote: > The DPDK API's are lax about checking for undefined flag values. > This makes it impossible to add new bits to existing API's > without causing ABI breakage. This means we end up doing unnecessary > symbol versioning just to work

[dpdk-dev] [PATCH v3 0/4] Enforce checking on flag values in API's

2020-04-27 Thread Stephen Hemminger
The DPDK API's are lax about checking for undefined flag values. This makes it impossible to add new bits to existing API's without causing ABI breakage. This means we end up doing unnecessary symbol versioning just to work around applications that might pass in naughty bits. This is the DPDK anal