From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Miroslav Rezanina <mrezanin@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
Dmitry Fleytman <dmitry.fleytman@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 1/2] Fix net.c warning on GCC 11
Date: Thu, 14 Jan 2021 14:15:59 +0100 [thread overview]
Message-ID: <4fd8d2a3-e665-4422-79e0-4e2a7337e4fc@redhat.com> (raw)
In-Reply-To: <dcb4bfa3fe810236475b338f2f6401ec3d1a1c57.1610607906.git.mrezanin@redhat.com>
+Jason +Dmitry
On 1/14/21 8:07 AM, Miroslav Rezanina wrote:
> When building qemu with GCC 11, compiling eth.c file produce following warning:
>
> warning: array subscript 'struct ip6_ext_hdr_routing[0]' is partly outside array bounds of 'struct ip6_ext_hdr[1]' [-Warray-bounds]
>
> This is caused by retyping from ip6_ext_hdr to ip6_ext_hdr_routing that has more
> attributes.
>
> As this usage is expected, suppress the warning temporarily through the function
> using this retyping.
This is not expected, this is a bug...
>
> Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
> ---
> net/eth.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/net/eth.c b/net/eth.c
> index 1e0821c5f8..b9bdd0435c 100644
> --- a/net/eth.c
> +++ b/net/eth.c
> @@ -405,6 +405,8 @@ _eth_get_rss_ex_dst_addr(const struct iovec *pkt, int pkt_frags,
> struct ip6_ext_hdr *ext_hdr,
> struct in6_address *dst_addr)
> {
> +#pragma GCC diagnostic push
> +#pragma GCC diagnostic ignored "-Warray-bounds"
> struct ip6_ext_hdr_routing *rthdr = (struct ip6_ext_hdr_routing *) ext_hdr;
eth_parse_ipv6_hdr() called iov_to_buf() to fill the 2 bytes of ext_hdr.
> if ((rthdr->rtype == 2) &&
Here we access after the 2 bytes filled... rthdr->rtype is somewhere on
eth_parse_ipv6_hdr's stack, its content is unknown.
> @@ -426,6 +428,7 @@ _eth_get_rss_ex_dst_addr(const struct iovec *pkt, int pkt_frags,
> }
>
> return false;
> +#pragma GCC diagnostic pop
Nacked-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2021-01-14 13:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 7:07 [PATCH v3 0/2] Fixing several GCC 11 warnings Miroslav Rezanina
2021-01-14 7:07 ` [PATCH v3 1/2] Fix net.c warning on GCC 11 Miroslav Rezanina
2021-01-14 13:15 ` Philippe Mathieu-Daudé [this message]
2021-01-14 14:19 ` Alexander Bulekov
2021-01-14 14:35 ` Philippe Mathieu-Daudé
2021-01-14 14:38 ` Miroslav Rezanina
2021-01-14 14:42 ` Alexander Bulekov
2021-01-14 15:09 ` Philippe Mathieu-Daudé
2021-01-14 14:36 ` Miroslav Rezanina
2021-01-14 7:07 ` [PATCH v3 2/2] s390x: Use strpadcpy for copying vm name Miroslav Rezanina
2021-01-14 8:32 ` Thomas Huth
2021-01-14 10:16 ` Cornelia Huck
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=4fd8d2a3-e665-4422-79e0-4e2a7337e4fc@redhat.com \
--to=philmd@redhat.com \
--cc=dmitry.fleytman@gmail.com \
--cc=jasowang@redhat.com \
--cc=mrezanin@redhat.com \
--cc=qemu-devel@nongnu.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).