From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH] net/tap: avoid memcpy with NULL arg
Date: Mon, 19 Aug 2024 08:10:08 -0700 [thread overview]
Message-ID: <20240819081008.5a9b121c@hermes.local> (raw)
In-Reply-To: <910231e7-6cd4-4da6-987e-1f97c7484018@amd.com>
On Mon, 19 Aug 2024 12:04:57 +0100
Ferruh Yigit <ferruh.yigit@amd.com> wrote:
> On 8/19/2024 12:03 PM, Ferruh Yigit wrote:
> > On 8/14/2024 3:34 AM, Stephen Hemminger wrote:
> >> Calling memcpy with a null pointer even if zero length is
> >> undefined, so check if data_length is zero.
> >> Problem reported by Gcc analyzer.
> >>
>
> Btw, how do you run the GCC analyzer?
> Is this something can we add to our CI checks?
I just added it to cflags in meson build.
Tap only had this warning, but mlx5 had lots of warnings.
prev parent reply other threads:[~2024-08-19 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 2:34 [PATCH] net/tap: avoid memcpy with NULL arg Stephen Hemminger
2024-08-19 11:03 ` Ferruh Yigit
2024-08-19 11:04 ` Ferruh Yigit
2024-08-19 15:10 ` Stephen Hemminger [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=20240819081008.5a9b121c@hermes.local \
--to=stephen@networkplumber.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.