All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Dash Four <mr.dash.four@googlemail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2] iproute2: lib/utils.c bug fixes
Date: Sun, 14 Apr 2013 10:00:00 -0700	[thread overview]
Message-ID: <20130414100000.3b73fa36@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <516AB8EE.5090901@googlemail.com>

On Sun, 14 Apr 2013 15:10:54 +0100
Dash Four <mr.dash.four@googlemail.com> wrote:

> This patch fixes the following 3 bugs in get_u32/get_u64 functions:
> 
>   1. On 32-bit systems, get_u32 could not detect an overflow.
>      get_u32(&l, "4294967296", 10) always returned 4294967295
>      (ULONG_MAX on 32-bit systems).
> 
>   2. get_u64(&ll, "4294967295", 10) was returning an error where
>      it shouldn't have (4294967295 is perfectly legitimate value for
>      unsigned long long).
> 
>   3. get_u64 couldn't detect an overflow errors (arg > ULLONG_MAX)
> 
> Changelog:
> 
> v2 - Dropped name title from Developer Certificate of Origin
> 
> Signed-off-by: Dash Four <mr.dash.four@googlemail.com>
> ---
>   lib/utils.c |    8 ++++++--
>   1 file changed, 6 insertions(+), 2 deletions(-)
> 

Thanks for your patch. there were lots of related over/underflow errors in
this code which have existed for a long time. I took your patch as motivation
and did multiple fixes to add error checking for all the cases present.

Thank you.

  reply	other threads:[~2013-04-14 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 14:10 [PATCH v2] iproute2: lib/utils.c bug fixes Dash Four
2013-04-14 17:00 ` Stephen Hemminger [this message]
2013-04-14 19:34   ` Dash Four
2013-04-14 19:37     ` David Miller
2013-04-14 19:22 ` David Miller

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=20130414100000.3b73fa36@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=mr.dash.four@googlemail.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.