On Tue, 2022-11-22 at 10:30 -0500, okaya@kernel.org wrote:
> From: Sinan Kaya <okaya@kernel.org>
> Following up the codeql reported problems first submittedby Stephen
> Hemminger here:
> https://lore.kernel.org/all/20220527161210.77212d0b@hermes.local/t/
> 
> Posting a series of fixes about potential null pointer accesses.
> Changes from v1:- Remove braces around single line statements- use
> NULL comparisons
> Sinan Kaya (11):  ethdev: check return result of
> rte_eth_dev_info_get  net/tap: check if name is null  memzone: check
> result of rte_fbarray_get  memzone: check result of
> malloc_elem_from_data  malloc: malloc_elem_join_adjacent_free can
> return null  malloc: check result of
> rte_mem_virt2memseg_list  malloc: check result of
> rte_fbarray_get  malloc: check result of rte_mem_virt2memseg  malloc:
> check result of malloc_elem_free  malloc: check result of
> elem_start_pt  bus/vdev: check result of rte_vdev_device_name
>  drivers/net/tap/rte_eth_tap.c        |  3 +++
> lib/eal/common/eal_common_memalloc.c |  5 ++++-
> lib/eal/common/eal_common_memzone.c  | 10 +++++++++-
> lib/eal/common/malloc_elem.c         | 14 +++++++++++---
> lib/eal/common/malloc_heap.c         |  9 ++++++++-
> lib/ethdev/ethdev_vdev.h             |  2 ++
> lib/ethdev/rte_class_eth.c           |  4 +++- 7 files changed, 40
> insertions(+), 7 deletions(-)
> 

Checking to see if I need to cover any feedback.