From: Sinan Kaya <okaya@kernel.org>
To: okaya@kernel.org, Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3 00/10] codeql fixes for various subsystems
Date: Mon, 06 Feb 2023 11:00:38 -0500 [thread overview]
Message-ID: <ff62f6a4001a24f809a552f79f12529ed2efdd8f.camel@kernel.org> (raw)
In-Reply-To: <20230120044140.95975-1-okaya@kernel.org>
On Thu, 2023-01-19 at 23:41 -0500, okaya@kernel.org wrote:
> From: Sinan Kaya <okaya@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(-)
>
Anatoly, any feedback on the series? You seem to be a maintainer for
2-9 patches.
next prev parent reply other threads:[~2023-02-06 16:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 4:41 okaya
2023-01-20 4:41 ` [PATCH v3 01/10] ethdev: check return result of rte_eth_dev_info_get okaya
2023-01-20 10:21 ` Morten Brørup
2023-01-20 4:41 ` [PATCH v3 02/10] memzone: check result of rte_fbarray_get okaya
2023-01-20 4:41 ` [PATCH v3 03/10] memzone: check result of malloc_elem_from_data okaya
2023-01-20 4:41 ` [PATCH v3 04/10] malloc: malloc_elem_join_adjacent_free can return null okaya
2023-01-20 4:41 ` [PATCH v3 05/10] malloc: check result of rte_mem_virt2memseg_list okaya
2023-01-20 4:41 ` [PATCH v3 06/10] malloc: check result of rte_fbarray_get okaya
2023-01-20 4:41 ` [PATCH v3 07/10] malloc: check result of rte_mem_virt2memseg okaya
2023-01-20 4:41 ` [PATCH v3 08/10] malloc: check result of malloc_elem_free okaya
2023-01-20 4:41 ` [PATCH v3 09/10] malloc: check result of elem_start_pt okaya
2023-01-20 4:41 ` [PATCH v3 10/10] bus/vdev: check result of rte_vdev_device_name okaya
2023-01-20 16:47 ` Stephen Hemminger
2023-01-22 20:51 ` Thomas Monjalon
2023-02-06 16:01 ` Sinan Kaya
2023-02-06 18:46 ` Thomas Monjalon
2023-02-06 16:00 ` Sinan Kaya [this message]
2023-07-06 22:43 ` [PATCH v3 00/10] codeql fixes for various subsystems Stephen Hemminger
2023-07-10 15:18 ` Sinan Kaya
2023-07-10 17:07 ` [PATCH v4 0/5] fixes for problems found by codeql analyzer Stephen Hemminger
2023-07-10 17:07 ` [PATCH v4 1/5] mailmap: add Sinan Stephen Hemminger
2023-07-10 17:07 ` [PATCH v4 2/5] ethdev: check return result of rte_eth_dev_info_get Stephen Hemminger
2023-12-16 10:06 ` Andrew Rybchenko
2023-12-16 10:08 ` Andrew Rybchenko
2023-07-10 17:07 ` [PATCH v4 3/5] memzone: check result of rte_fbarray_get and malloc_elem_from_data Stephen Hemminger
2023-07-10 17:07 ` [PATCH v4 4/5] malloc: codeql fixes Stephen Hemminger
2023-07-10 17:08 ` [PATCH v4 5/5] bus/vdev: check result of rte_vdev_device_name Stephen Hemminger
2023-12-16 10:10 ` Andrew Rybchenko
2023-07-11 1:37 ` [PATCH v4 0/5] fixes for problems found by codeql analyzer fengchengwen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff62f6a4001a24f809a552f79f12529ed2efdd8f.camel@kernel.org \
--to=okaya@kernel.org \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).