From: Sinan Kaya <okaya@kernel.org>
To: dev@dpdk.org
Subject: Re: [PATCH RESEND v2 00/11] codeql fixes for various subsystems
Date: Tue, 13 Dec 2022 11:43:01 -0500 [thread overview]
Message-ID: <750bb3b53fe0521b1850a49666aba09d5d9565cf.camel@kernel.org> (raw)
In-Reply-To: <20221122153053.1172434-1-okaya@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 2287 bytes --]
next prev parent reply other threads:[~2022-12-13 16:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 15:30 okaya
2022-11-22 15:30 ` [PATCH RESEND v2 01/11] ethdev: check return result of rte_eth_dev_info_get okaya
2023-01-18 8:42 ` Thomas Monjalon
2023-01-19 5:22 ` Sinan Kaya
2023-01-19 14:20 ` Ferruh Yigit
2022-11-22 15:30 ` [PATCH RESEND v2 02/11] net/tap: check if name is null okaya
2023-01-18 10:57 ` Ferruh Yigit
2023-01-19 5:21 ` Sinan Kaya
2022-11-22 15:30 ` [PATCH RESEND v2 03/11] memzone: check result of rte_fbarray_get okaya
2022-11-22 15:30 ` [PATCH RESEND v2 04/11] memzone: check result of malloc_elem_from_data okaya
2022-11-22 15:30 ` [PATCH RESEND v2 05/11] malloc: malloc_elem_join_adjacent_free can return null okaya
2022-11-22 15:30 ` [PATCH RESEND v2 06/11] malloc: check result of rte_mem_virt2memseg_list okaya
2022-11-22 15:30 ` [PATCH RESEND v2 07/11] malloc: check result of rte_fbarray_get okaya
2022-11-22 15:30 ` [PATCH RESEND v2 08/11] malloc: check result of rte_mem_virt2memseg okaya
2022-11-22 15:30 ` [PATCH RESEND v2 09/11] malloc: check result of malloc_elem_free okaya
2022-11-22 15:30 ` [PATCH RESEND v2 10/11] malloc: check result of elem_start_pt okaya
2022-11-22 15:30 ` [PATCH RESEND v2 11/11] bus/vdev: check result of rte_vdev_device_name okaya
2022-12-13 16:43 ` Sinan Kaya [this message]
2022-12-13 16:59 ` [PATCH RESEND v2 00/11] codeql fixes for various subsystems Dmitry Kozlyuk
2022-12-13 17:02 ` Sinan Kaya
2022-12-16 15:26 ` Sinan Kaya
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=750bb3b53fe0521b1850a49666aba09d5d9565cf.camel@kernel.org \
--to=okaya@kernel.org \
--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).