[PATCH] net/tap: avoid memcpy with NULL arg
Stephen Hemminger
stephen at networkplumber.org
Mon Aug 19 17:10:08 CEST 2024
On Mon, 19 Aug 2024 12:04:57 +0100
Ferruh Yigit <ferruh.yigit at 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.
More information about the dev
mailing list