Re: [dpdk-dev] [PATCH v2] net: be more restrictive in accepted ether string formats

2019-07-19 Thread Ferruh Yigit
On 7/19/2019 2:42 PM, Olivier Matz wrote: > On Thu, Jul 18, 2019 at 11:35:44AM -0700, Stephen Hemminger wrote: >> The current ether_unformat_addr code was based off of >> BSD ether_aton. That version changed what was allowed >> by the cmdline ether address parser. >> For example, it allows dropping

Re: [dpdk-dev] [PATCH v2] net: be more restrictive in accepted ether string formats

2019-07-19 Thread Olivier Matz
On Thu, Jul 18, 2019 at 11:35:44AM -0700, Stephen Hemminger wrote: > The current ether_unformat_addr code was based off of > BSD ether_aton. That version changed what was allowed > by the cmdline ether address parser. > For example, it allows dropping leading zeros. > > Change the code to be more

[dpdk-dev] [PATCH v2] net: be more restrictive in accepted ether string formats

2019-07-18 Thread Stephen Hemminger
The current ether_unformat_addr code was based off of BSD ether_aton. That version changed what was allowed by the cmdline ether address parser. For example, it allows dropping leading zeros. Change the code to be more restrictive and only allow the fully expanded standard formats. Bugzilla ID: 3