From: David Marchand <david.marchand@redhat.com>
To: Marat Khalili <marat.khalili@huawei.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Zhirun Yan <yanzhirun_163@163.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Robin Jarry <rjarry@redhat.com>,
dev@dpdk.org
Subject: Re: [PATCH v2 1/2] lib/graph: lib/graph: fix memset with NULL
Date: Mon, 23 Jun 2025 14:06:20 +0200 [thread overview]
Message-ID: <CAJFAV8zdPShwqG6iahrnzPRX+SkVdM3h6beBj+P7vxLB58vt0g@mail.gmail.com> (raw)
In-Reply-To: <20250617151339.28794-1-marat.khalili@huawei.com>
On Tue, Jun 17, 2025 at 5:14 PM Marat Khalili <marat.khalili@huawei.com> wrote:
>
> This was flagged by undefined behaviour sanitizer: memset should not be
> called with NULL first argument. (memset requires first argument to be
> pointer to a memory object, so passing NULL may result in an undefined
> behaviour including among other things optimizer potentially removing
> code paths depending on stat->xstat_count being NULL.)
>
> Sanitizer message:
>
> lib/graph/graph_stats.c:473:2: runtime error: null pointer passed as
> argument 1, which is declared to never be null
>
> To fix the issue add a check that stat->xstat_count is not NULL before
> the call.
>
> Fixes: 070db97e017 ("graph: support node xstats")
>
> Signed-off-by: Marat Khalili <marat.khalili@huawei.com>
> ---
>
> v2: Following the suggestions from Jerin Jacob changed the Subject and
> added Fixes line.
>
> lib/graph/graph_stats.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/lib/graph/graph_stats.c b/lib/graph/graph_stats.c
> index eac73cbf71..57cd72e7cc 100644
> --- a/lib/graph/graph_stats.c
> +++ b/lib/graph/graph_stats.c
> @@ -470,7 +470,9 @@ cluster_node_arregate_stats(struct cluster_node *cluster, bool dispatch)
> uint64_t *xstat;
> uint8_t i;
>
> - memset(stat->xstat_count, 0, sizeof(uint64_t) * stat->xstat_cntrs);
> + if (stat->xstat_count != NULL)
I would check against stat->xstat_cntrs since the array is allocated
based on this count.
This will be more consistent with the loop on this same counter later
in this function.
> + memset(stat->xstat_count, 0,
> + sizeof(uint64_t) * stat->xstat_cntrs);
No need for going to a new line.
> for (count = 0; count < cluster->nb_nodes; count++) {
> node = cluster->nodes[count];
>
Thanks for the fix.
--
David Marchand
prev parent reply other threads:[~2025-06-23 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 15:13 Marat Khalili
2025-06-17 15:13 ` [PATCH v2 2/2] lib/graph: default-align rte_graph_cluster_stats Marat Khalili
2025-06-17 15:27 ` Jerin Jacob
2025-06-17 15:41 ` Marat Khalili
2025-06-17 15:49 ` Jerin Jacob
2025-06-17 16:39 ` Marat Khalili
2025-06-23 8:52 ` Marat Khalili
2025-06-23 12:07 ` David Marchand
2025-06-23 12:18 ` Marat Khalili
2025-06-23 15:39 ` Morten Brørup
2025-06-23 12:06 ` David Marchand [this message]
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=CAJFAV8zdPShwqG6iahrnzPRX+SkVdM3h6beBj+P7vxLB58vt0g@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=marat.khalili@huawei.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=rjarry@redhat.com \
--cc=yanzhirun_163@163.com \
/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).