public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Petr Machata <petrm@nvidia•com>
To: Stephen Hemminger <stephen@networkplumber•org>
Cc: <netdev@vger•kernel.org>, <petrm@mellanox•com>
Subject: Re: [PATCH 3/5] tc: fix compiler warnings in ip6 pedit
Date: Tue, 1 Dec 2020 00:10:18 +0100	[thread overview]
Message-ID: <87zh2yo2zp.fsf@nvidia.com> (raw)
In-Reply-To: <20201130002135.6537-4-stephen@networkplumber.org>


Stephen Hemminger <stephen@networkplumber•org> writes:

> Gcc-10 complains about referencing a zero size array.
> This occurs because the array of keys is actually in the following
> structure which is part of the overall selector.
>
> The original code was safe, but better to just use the key
> array directly.
>
> Fixes: 2d9a8dc439ee ("tc: p_ip6: Support pedit of IPv6 dsfield")
> Cc: petrm@mellanox•com
> Signed-off-by: Stephen Hemminger <stephen@networkplumber•org>

Reviewed-by: Petr Machata <petrm@nvidia•com>

  reply	other threads:[~2020-11-30 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  0:21 [PATCH 0/5] Fix compiler warnings from GCC-10 Stephen Hemminger
2020-11-30  0:21 ` [PATCH 1/5] devlink: fix uninitialized warning Stephen Hemminger
2020-11-30  0:21 ` [PATCH 2/5] bridge: fix string length warning Stephen Hemminger
2020-11-30  0:21 ` [PATCH 3/5] tc: fix compiler warnings in ip6 pedit Stephen Hemminger
2020-11-30 23:10   ` Petr Machata [this message]
2020-11-30  0:21 ` [PATCH 4/5] misc: fix compiler warning in ifstat and nstat Stephen Hemminger
2020-11-30  9:18   ` David Laight
2020-11-30 17:31     ` Stephen Hemminger
2020-11-30  0:21 ` [PATCH 5/5] f_u32: fix compiler gcc-10 compiler warning Stephen Hemminger
2020-11-30 19:21 ` [PATCH 0/5] Fix compiler warnings from GCC-10 Jacob Keller
2020-12-03 16:40 ` patchwork-bot+netdevbpf

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=87zh2yo2zp.fsf@nvidia.com \
    --to=petrm@nvidia$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=petrm@mellanox$(echo .)com \
    --cc=stephen@networkplumber$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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