From: Petr Machata <petrm@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <netdev@vger.kernel.org>
Subject: Re: [RFC] iproute2: ipila warning
Date: Tue, 3 Oct 2023 11:35:47 +0200 [thread overview]
Message-ID: <87o7hgqb3w.fsf@nvidia.com> (raw)
In-Reply-To: <20231002144014.40c33922@hermes.local>
Stephen Hemminger <stephen@networkplumber.org> writes:
> Building current code with Debian stable Gcc 12.2.0 see this warning.
>
> CC ipila.o
> ipila.c: In function ‘print_ila_locid’:
> ipila.c:57:32: warning: ‘addr’ may be used uninitialized [-Wmaybe-uninitialized]
> 57 | v = ntohs(words[i]);
> | ^
> ipila.c:69:13: note: ‘addr’ declared here
> 69 | static void print_ila_locid(const char *tag, int attr, struct rtattr *tb[])
> | ^~~~~~~~~~~~~~~
>
> Looks like a Gcc aliasing bug.
> Relevant snippets.
>
> static void print_addr64(__u64 addr, char *buff, size_t len)
> {
> __u16 *words = (__u16 *)&addr;
> __u16 v;
> int i, ret;
> size_t written = 0;
> char *sep = ":";
>
> for (i = 0; i < 4; i++) {
> v = ntohs(words[i]);
> ...
>
>
> static void print_ila_locid(const char *tag, int attr, struct rtattr *tb[])
> {
> char abuf[256];
>
> if (tb[attr])
> print_addr64(rta_getattr_u64(tb[attr]),
> abuf, sizeof(abuf));
>
> One solution would be to use a union.
> Other would be to use some variation of no-strict aliasing.
>
> --- a/ip/ipila.c
> +++ b/ip/ipila.c
> @@ -47,14 +47,17 @@ static int genl_family = -1;
>
> static void print_addr64(__u64 addr, char *buff, size_t len)
> {
> - __u16 *words = (__u16 *)&addr;
> + union {
> + __u64 w64;
> + __u16 words[4];
> + } id = { .w64 = addr };
This looks OK to me FWIW. Unions are commonly used to legalize aliasing,
so anybody looking at this will understand what's going on.
> __u16 v;
> int i, ret;
> size_t written = 0;
> char *sep = ":";
>
> for (i = 0; i < 4; i++) {
> - v = ntohs(words[i]);
> + v = ntohs(id.words[i]);
>
> if (i == 3)
> sep = "";
> ..
prev parent reply other threads:[~2023-10-03 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 21:40 [RFC] iproute2: ipila warning Stephen Hemminger
2023-10-03 9:35 ` Petr Machata [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=87o7hgqb3w.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=netdev@vger.kernel.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).