From: Stephen Hemminger <stephen@networkplumber.org>
To: Petr Machata <petrm@nvidia.com>
Cc: <netdev@vger.kernel.org>, David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH iproute2] ip: Fix size_columns() invocation that passes a 32-bit quantity
Date: Mon, 27 Jun 2022 08:14:21 -0700 [thread overview]
Message-ID: <20220627081421.3228af32@hermes.local> (raw)
In-Reply-To: <1b8c8a3e8ae41a85f2167d94a6d7bcc4d46757f6.1656335952.git.petrm@nvidia.com>
On Mon, 27 Jun 2022 15:20:01 +0200
Petr Machata <petrm@nvidia.com> wrote:
> In print_stats64(), the last size_columns() invocation passes number of
> carrier changes as one of the arguments. The value is decoded as a 32-bit
> quantity, but size_columns() expects a 64-bit one. This is undefined
> behavior.
>
> The reason valgrind does not cite this is that the previous size_columns()
> invocations prime the ABI area used for the value transfer. When these
> other invocations are commented away, valgrind does complain that
> "conditional jump or move depends on uninitialised value", as would be
> expected.
>
> Fixes: 49437375b6c1 ("ip: dynamically size columns when printing stats")
> Signed-off-by: Petr Machata <petrm@nvidia.com>
> ---
> ip/ipaddress.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/ip/ipaddress.c b/ip/ipaddress.c
> index 5a3b1cae..8cd76073 100644
> --- a/ip/ipaddress.c
> +++ b/ip/ipaddress.c
> @@ -788,8 +788,9 @@ void print_stats64(FILE *fp, struct rtnl_link_stats64 *s,
> s->tx_aborted_errors, s->tx_fifo_errors,
> s->tx_window_errors,
> s->tx_heartbeat_errors,
> - carrier_changes ?
> - rta_getattr_u32(carrier_changes) : 0);
> + (uint64_t)(carrier_changes ?
> + rta_getattr_u32(carrier_changes)
> + : 0));
Looks good, but would be clearer with a local temporary variable
which would eliminate the cast etc.
next prev parent reply other threads:[~2022-06-27 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 13:20 [PATCH iproute2] ip: Fix size_columns() invocation that passes a 32-bit quantity Petr Machata
2022-06-27 15:14 ` Stephen Hemminger [this message]
2022-06-27 16:06 ` Petr Machata
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=20220627081421.3228af32@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
/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).