On Thu, 19 Jan 2023 23:41:30 -0500 ok...@kernel.org wrote: > From: Sinan Kaya <ok...@kernel.org> > > Following up the codeql reported problems first submitted > by 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 v3: > - Dropped net/tap: check if name is null > - Moved the comment to the appropriate position in ethdev: check return > result of rte_eth_dev_info_get > > Changes from v2: > - Remove braces around single line statements > - use NULL comparisons > > > Sinan Kaya (10): > ethdev: check return result of rte_eth_dev_info_get > 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 > > 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 +++- > 6 files changed, 37 insertions(+), 7 deletions(-)
The patches are fine, only warning was from the requirement that all submitters be in .mailmap now. Do you mind if I rebase these, add a mailmap and combine the like ones together? Acked-by: Stephen Hemminger <step...@networkplumber.org>
