[dpdk-dev] [PATCH] eal devargs: don't call rte_log when not initialized

> > This problem was discovered when passing invalid PCI id to the > > blacklist API in devargs. > > > > Any failures in rte_devargs_add would cause a core dump because > > it would call rte_log() before the the EAL log environment was > > initailized. Rather than try and log just remove the mess

[dpdk-dev] [PATCH] eal devargs: don't call rte_log when not initialized

Hi Stephen, On 05/15/2015 06:37 PM, Stephen Hemminger wrote: > This problem was discovered when passing invalid PCI id to the > blacklist API in devargs. > > Any failures in rte_devargs_add would cause a core dump because > it would call rte_log() before the the EAL log environment was > initaili

[dpdk-dev] [PATCH] eal devargs: don't call rte_log when not initialized

This problem was discovered when passing invalid PCI id to the blacklist API in devargs. Any failures in rte_devargs_add would cause a core dump because it would call rte_log() before the the EAL log environment was initailized. Rather than try and log just remove the messages and leave it up to