From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH] net/tap: avoid memcpy with NULL arg
Date: Mon, 19 Aug 2024 12:03:35 +0100 [thread overview]
Message-ID: <559f1db2-395e-4d93-ba63-650cfed481eb@amd.com> (raw)
In-Reply-To: <20240814023426.124491-1-stephen@networkplumber.org>
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.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2024-08-19 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 2:34 Stephen Hemminger
2024-08-19 11:03 ` Ferruh Yigit [this message]
2024-08-19 11:04 ` Ferruh Yigit
2024-08-19 15:10 ` Stephen Hemminger
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=559f1db2-395e-4d93-ba63-650cfed481eb@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).