devargs: fix crash on failure
devargs: fix crash on failure

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
initialized.  Rather than try and log just remove the messages
and leave it up to the caller to check the return value.

Most of the other failure possibilities are when malloc() fails, and if
that happens any logging that used malloc() would also fail.

This failure was not caught by the standalone tests to devargs
because the tests are run after calling rte_eal_init (which is not
how devargs is intended to be used).

Signed-off-by: Stephen Hemminger <06fa905d7f2aaced6dc72e9511c71a2a51e8aead@networkplumber.org>
Acked-by: Olivier Matz <dfcc1510895413197abb4336e39bb0a3906cba71@6wind.com>

tsphillips/dpdk-fork,john-mcnamara-intel/dpdk,john-mcnamara-intel/dpdk,john-mcnamara-intel/dpdk,tsphillips/dpdk-fork,venkynv/dpdk-mirror,venkynv/dpdk-mirror,venkynv/dpdk-mirror,msune/dpdk,tsphillips/dpdk-fork,msune/dpdk,tsphillips/dpdk-fork,msune/dpdk,msune/dpdk,mixja/dpdk,mixja/dpdk,mixja/dpdk,john-mcnamara-intel/dpdk,venkynv/dpdk-mirror,mixja/dpdk